A dual disk setup for ZFS (or any other kind of RAID) is super wasteful.
Based on what? I’ve been running ZFS since it was Solaris-only and raidz1/raidz2 are OK, but they come with complexity and performance penalties, and they’re somewhat less portable than a mirror. There are many advantages to simple mirrors: first-response reads, block correction, scrubs, etc.
Scripting it isn’t that tricky.
I’m old and use rsync, with mtime and not(!) operands and I’m able to keep 7 daily, 4 weekly, and 4 monthly backups. Runs every day, the rest of the backups are pruned in this rolling window.
Gate-keeping is a strong word… It also implies that people on the other side of the gate learned something to get there.
20 years ago we were doing what we could manually, and learning the hard way. The tools have improved and by now do most of the heavy lifting for us. And better tools will come along to make things even easier/better. That’s just the way it works.
Compare self-hosting to doing your own mechanic work on a vehicle: there are a lot of tasks that most ppl would benefit from learning the diy way to do it, but there are dangers to car repair that will never go away, like proper car support with jacks, securing wheels correctly, etc.
It would be neglectful for the community to say nothing and send ppl off to get pwned.
My range to the next node is 7 miles.
Lucky you. I’ve got max about 900m (about half mile) by putting a node up on the mountain near me, and that was intermittent and message transmissions were delayed between 5 and 10 min.
Like I said, great if it works. Not a whole lot of good use cases, and op’s is not a good use case.
AirTags work because there is a huge network of apple devices registering BT beacons. Meshtastic isn’t really viable unless there are other nodes around on the same channel, as you mentioned.
I have tried to use two LilyGo t-echos to GPS track my dog. Range is really poor in the mountains, so I basically couldn’t see the collared device unless it was within 100 to 150m away, which isn’t really helpful.
In a bigger urban area, more nodes didn’t help unless I was on the default channel, so same problem again, this timeline extra emf pollution.
Meshtastic is a great idea, but use cases are really limited.
I moved from pihole to technitium roughly two years ago. I was tired of pihole not doing “adult” DNS things, like zone transfers. Technitium is a real DNS server, pihole is just a resolver. You can create actual soa and srv records with technitium.
It already could sync zones, I’ve been doing primary -> secondary zone transfers for at least two years.
It didn’t sync lists and other configs, though. That’s new.
Edit: sorry, I misread the question. I haven’t run into any docker containers that don’t run on incus, but my testing is limited.
Well, I have run the homeassistant core docker, calibre web automated, and a bunch more.
One just needs to add the docker https path to its repository and the rest is just translating the options to the way incus starts these. (Sorry, I can’t exactly remember what incus uses to run these containers.)
Anyway, I can dig up some helpful documentation if you’re rally interested.
I moved to incus from proxmox nearly 18 months ago and I haven’t looked back.
Yes, sorry. I meant incus, not incus os.
IncusOS supports OCI containers, which means it can run most docker containers natively. And LXC, and vms via QEMU/KVM.
Oh, OK! Brilliant, I will check on this and report back.
Tempus is great, good job.
Very nice.
I’m afraid to ask, but I can’t seem to figure out how to add an http stream to the radio section… Is this feature active?
Also I don’t think Proxmox cares about storage either,
Proxmox forces you to add a “storage area”, which is fine, except you must use their mount path of /mnt/pve/ and you must add NFS tuning switches via pve or they don’t work.
Proxmox is great, I used it for 8 years. But it is also opinionated and doesn’t like non-standard configs.
Fair enough!
Like I said, incus don’t care about your storage.
I’ve never used PBS, I’ve always just rolled my own. I currently keep 7 daily, 4 weekly and 4 monthly. My data mounts are all nfsv4.
Edit: isnt it possible to use pbs with non-proxmox systems?
Don’t use Proxmox, use incus. It’s way easier to run and doesn’t give a care about your storage.
Once you get to know the GUI well enough and start scripting, the GUI becomes less relevant.
Is this separate from a bind mount? Cause that doesn’t happen with bind mounts.
Yeah, I read this article twice now, and the only identifiable wrongdoing on FUTO’s part is donating to FOSS projects without using their “institutional practice”… Which is a bizarre complaint.
The article is rife with “something ain’t right at FUTO”, but fails to wrap words around that statement.
Hard disagree, and it is one of the best things about ZFS. You can plunk a ZFS pool on another system and be almost certain it will import. Systems die. Having been through several data-loss incidents, I find it is much preferable to be able to pull 1 disk than have to drag out 2 or three to transplant a ZFS pool.
Regarding the scrubs, I was trying to indicate that ZFS is more than just a raid manager, there are advantages to ZFS on even a single disk.
If that were entirely true, striping would be the most popular ZFS pool arrangement, since you get performance and max storage.
Edit: this was not to say “you’re wrong”, just different approaches to storage.