Opensense is often bound by single-core operations depending on where a network packet may plumb itself through the kernel. A great example is any PPPoE connections on the base OS BSD. Vyos doesn’t have these same limitations since it’s minted on Linux - which supports traffic steering.
Really though, IaC for vyos has always been rock solid. Even though the persistent config in Opnsense is cool, adding new features or configs can be a bit of a pain in the ass
Stripped back into the mid 2000s luxury, where they’ve finally mandated backup cameras as a safety requirement.
Decade running arch on a laptop w encrypted drives, the only fails were from powerdevil.
This is less math and more physics - which is math with rules
Right, probably a mix of hydro and potted indoor grows. They’re almost all probs well sealed and atmo regulated so not a lot of contaminants to infiltrate the bud. Aka, in your area unless you want to grow for the joy of it it may not be worth it.
However!!! You should totally start a micro grow in a red solo cup and post updates :) you can clean metadata from the photo by texting it to yourself in the Signal messenger app if you’re worried about that. Otherwise, good luck and great bud!
You’re in Arizona with a bunch of hydro grows, so not likely. It’s really only noticeable when the local bud is predominantly from outdoor crops…. It is a bunch of fun to grow though 😊
First time growing this season, so it’s awesome to see where everyone else is at!
That’s the top end, you have to look at the bottom-end to understand the impacts to those marginalized populations - youths and seniors.
I gave the example of PPPoE, the other option is to read the linked kernel docs to understand traffic steering and infer where those situations could occur.