

Exactly. A day in the life of Homelander.
Exactly. A day in the life of Homelander.
Honestly, there were so many fundamental changes in the 13 upgrade for certain packages that I had to fix on a couple of machines that I’d be hesitant to try no-scoping the 11 > 13 upgrade.
I flew by the seat of my pants and managed to pull off 10 directly to 12, but I wouldn’t do it for this one.
No.
By itself, apt will give you headaches.
Debian migrated to new paths for security non-free firmware in repositories from 11 to 12, and apt goes to v3 in 12 to 13, which changes the format of sources. There is a new apt modernize-sources command, but it assumes your paths are correct.
If you know what you’re doing, you can do this by correcting the repo paths and do the without-new-packages upgrade, but be prepared to fix apt.
If you’re a casual user, maybe stick with 11>12>13.
If the target is zfs, use zfs send. If the target is anything else, rsync.
Schedule it with cron.
Be aware that with zfs snapshots, you need to replay them to restore, which means you’ll periodically need to do a full backup. ClaraSystems has a number of guides on how to create zfs datasets to make efficient backups the way you want.
Edit: KlaraSystems, sorry.
I had a very old install, migrated from 2016. It broke on nearly every upgrade, where I’d have to invoke some occ command to fix the db. It was more work than was worth having Nextcloud.
Now I have syncthing and radicale.
Radicale. I just finished setting it up and with that, I can now finally shut down Nextcloud.
I don’t think they want to bother with the administration, they were forced to to stop anyone from spamming from random SMTP servers.
Because of dmarc and DKIM, we don’t really need this anymore, but there were good reasons for it.
In general, follow samba’s tunjng guidelines, particularly what not to set.
This list is terrible. These are all “Ai-powered” apps that have mostly better and established alternatives.
Wow, what a great response!
OK, you’ve sold me, I’ll sign up and try it.
Your personal willingness to explain your philosophy of the service is what swayed me, and I think that will go a long way in other forums and sites to pick up new subscribers.
I like this, and I’m willing to give it a shot.
Edit: I’d be happy to pay for mail as a service if it works for me.
Plex isn’t perfect, but jellyfin X Y Z
Really, my guy? You forget that Plex takes things away after saying they wouldn’t? You’re happy with your paid Plex pass… Until Plex decides one day that your pass isn’t lifetime anymore. Or that it doesn’t cover the features it used to. And yes, Plex has lied about this before. That’s why so many ppl are pissed at Plex.
And please give an example of “jellyfin being held back”, whatever that means.
Ethan Sholly, if you don’t know anything about how FOSS works, just listen and stop talking.
I went the other way; I had a Dell r430 and downsized to two hp elitedesk g4 mini. Together, they use less than half of the power of the 1u server.
But I am never satisfied, I’m sure I’ll want to iterate again next year.
On what platform?
I believe that when the bubble bursts, education will be one genuine usecase for LLMs.
When the bubble bursts, what will survive is what makes money. Education doesn’t make money unless it’s in the national interest.
Sure, I can accept that.
I don’t particularly have an opinion on artist compensation vs listener freedom when it comes to this. Obviously, I would prefer artists were paid what they deserve, but I don’t like participating in the fallacy that the end user is ethically responsible for the bullshit music industry infrastructure not paying artists properly.
I give where I can, but I’m just some person.
I think like this solution the best.
Not if you’re buying them 2nd hand on eBay, which would represent the bulk of building a collection.
To be clear, im not trying to detract from the effort, it’s just op mentioned artists not getting paid what they deserve.
Iptables (and nftables, among others) is just an implementation of netfilter kernel modules.
Yes, since Tailscale is based on wireguard.
Probably not the best practice, though, since any device that connects will be allowed to use the service if there is no authentication on the cert.