It’s better to think about it as though you are making a queue of changes that need approval to be permanent. Rather than just accepting that you just installed a ton of dependencies for no reason because you didn’t really want the software, you can cleanly reverse any of the changes.
In a sense, it accomplishes a similar thing as nix in a different way.
it’s not like sD devs forced them to adopt their option
It kind of is, though. You dont typically select your preboot environment, it’s selected for you.
You have already identified the problem in the logs.
You have a fake drive with firmware that says 1.8tb but are actually much lower.
access beyond end of device
This means an inode is mapped to a non-existing sector. Get your money back, if you still can.
Yeah, but things like human readable logs are almost all gone because of journalctl changes that went into the systemd ecosystem without anyone really running by folks who look at logs everyday.
It’s not the functionality of systemd I don’t like, it’s the Poettering way of just making changes to stuff without bothering to learn how any of the rest of us professionally use things.
In tempus, the setting is called “continuous play”. In feishin, it’s called “auto-dj”. Both settings are turned on by default, so you shouldn’t have to do anything.
Scrobbling helps because every played track goes into played history, and play counts help dynamic song selection more and more over time.
I don’t use the ratings, but I’ll “heart” songs I like.
I scrobble my playing from navidrome using listenbrainz and tell my two clients Tempus and Feishin to use the scrobbled data to build dynamic playlists. If I start with a particular song or album, the mix following that is usually kept in the same mood, only strays into weird stuff once in a while, but no more that YouTube Music used to.
Mir was canonical’s own fault for trying to pull a (blatantly obvious) licensing move where Mir would have been nearly impossible to compete with in a future Ubuntu.
And that’s setting aside the absolutely insane statements canonical’s Mir team were making about Wayland at the time.
When you fumble something so badly that Intel stops supporting your efforts on it in protest, you messed up.
I mean, there’s a difference between not gatekeeping when talking about cloudflare and completely waving Cloudflare’s banner on your front lawn.
So yeah, I wouldn’t have phrased it the way original comment was phrased, but holy cow, bro… Cloudflare is far from perfect and the people that will have existential problems with Cloudflare are very likely to be self-hosters.
Don’t run before you can walk.
Fstab is how it works in the background, best to learn that first.
Yeah, that’s fine too. I’m being facetious, I don’t actually care that much. I just know B at this point, 30 years later.
Haha, I don’t really know, it just seems easier to remember.
B or death.
So long as my mortal body can pull drops, it will be B. Or you’re fired.
My friend, I am a daily user of tempus and it is amazing.
Late to reply here, but I set this up and it’s pretty great. The space savings is cool, but what I like is the compatibility with various Jellyfin player apps is much better. I had a number of files with over twenty subtitle tracks all labelled “undetermined”. Using subtitles on these episodes on certain (Roku) versions of Jellyfin player was an unpleasant experience. Muxarr cleaned that all up.
Mint is pretty polished and mostly stays out of the way. I think that was probably a good choice, looking at your style of shifting over components of your workflow.
Could be.
Speedtest (the ookla one) uses a bunch of traceroute and compares hops to pick a peering point, but they display your public IP on the test page and probably use some icanhzip or other service to know that. It should come as no surprise to you that most north American ISPs pay Ookla to prefer peering points in which they have a heavy presence.
Icanhazip is an older service, I’m surprised cloudflare didn’t just kill it, they built their own when they were standing up 1.1.1.1.
Could also be some other tooling on your lan built before the Claude days.
The back story of icanhazip is OK, but I want to know where you picked it up in your logs… Incoming on edge? Something in your network dialing out?
You’re a programmer, what would you recommend?
Hah! By trade, I’m a sysadmin, my daily is security reviews at the planning and governance level.
I spent a good 6 years working in a Dev shop, and I picked up a lot of habits there, learned a ton about rest APIs, etc.
Setting up a vault for secrets (Hashicorp’s vault is a popular one) might be a bit overkill for your needs in a homelab, but it’s a great way to inject some security into python, bash scripts, which I think is useful, because lots of us start with scripting and move from there.
The basic mechanism is you set up the vault, define pools, etc and then use a token request instead of putting the secret in the script itself. There are tons of examples for each language and mode, but i just use a vault command in the script, throw the output in a variable and that’s pretty much it.
Secrets management in Dev and devops work is really interesting, if you ask me. All the way from the IDE to prod, there are many ways to leak passwords, api tokens, paths no one should know, etc.
Edit: I hope you didn’t take the vault comment as an admonishment, I meant it to be an interesting suggestion.
Edit 2: sometimes I wish I could go back to more technical stuff, that’s pretty much my reason for doing homelab stuff.
Well, it’s not super difficult. I sort of mash my way through getting data by api by just using curl and then clumsily filtering the output.
You’ve already got the mechanism to get the data, I think your solution is fine. My way to do it is just a relic from my time working with a bunch of devs.
Calibre Web Automated. I have Kobo integration enabled, so when I add an ebook to the “sync” folder, it appears on my Kobo. pretty nice system.