- Debian is a dependency hell, otherwise fine.
I agree on the older packages (I don’t need cutting edge), but what do mean about “dependency hell”?
Side note, I laughed a bit at this, I haven’t heard the term “dependency hell” since the old rpm editor hat days before yum.
Portability is not really an aspect one needs to consider when it comes to a NAS
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.
for a home NAS, the goal is maximising data storage capacity without a major hit on performance
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.
You can passthrough more than one device at a time. This is probably the source of your slow speeds.
Add a virtual nic to the opnsense VM and bind it to the host bridge, that way you can use both the VM network and the physical LAN without a lot of faf.
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.
deleted by creator
Holy moly… I’m sitting on a couple of installs I’ve upgraded from 2016. I’m too lazy to reinstall.
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.
Are you not discussing factors to a successful foray by steam into VR?
Steam doesn’t win users and marketshare because of your needs. Or even hardware. It wins users because the steam library is already on the device.
I’ve used Linux since 1998, and several DEs. I’ve never heard the Windows key referred to as a “meta” key.
Hold super and right-click a window to resize it. Ymmv
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.
deleted by creator
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.
deleted by creator
Then you will have to do it with bridging.
Create a second bridge and bind only the wan interface and the physical interface of opnsense to it. Then create a 2nd interface for opnsense, but bind it to the brIdge libvirt uses to connect its guests.