pyvpx

pfSense is a re-packaged FreeBSD. you'll find pfSense doesn't support as wide a variety of platforms (anything MIPS) or wireless cards.

so many middleboxes out there, unfortunately. I've had success with both GRE and LISP tunnels in addition to utilizing MPTCP.

yes, but where the equipment is physically located is often of the most importance.

Verizon Wireless outsources literally everything but customer service. Everything.

because fantasy investing is fundamentally a prediction market (IMO)

I would argue it's not a proper market place, fantasy or not, without such ability. (meaning, whatever values or data that comes from this is of near zero utility without the ability to short)

> I'm merely asking that postgres wraps more automation and convenience around the things that it already does.

and if history is any indication, it will when it's good and ready to be convenient and automated. as a previous poster (or two) most eloquently noted, postgres tends to work from the bottom up. when the "fundamentals" have been hashed out and thoroughly tested through all or nearly all edge cases, then convenient interfaces "bubble up"

and hey, your patches are always welcomed :)

you're both being downvoted because you're both completely wrong. it turns out permissively licensed, security-focused, and easy to maintain code bases aren't easy to find outside of OpenBSD. so sometimes they have to write their own.

say, a packet filter, for example...

I imagine you could use one of the various streaming replication solutions to avoid the "halt" part. pure speculation on my part, however.

yes, it's really neat. then the more you dig into it the more you realize literally everything and the kitchen sink is patented to all hell and back.

best of luck using any of it without a large team of expensive lawyers.

please do not link to calomel.org. OpenBSD takes great care to have clear, concise, accurate documentation available both on the system and on the web. link to the man page!

calomel.org is filled with...ignorance, to say the least.

considering you wrote a book on OpenBSD many moons ago, you'd know that the only things that get attention are the itches /developers/ scratch. since you seem to be happy not being apart of the OpenBSD "world" (aka not developing on or for OpenBSD), who other than yourself really cares what you feel are higher priority needs and gaps?

you can do that as well.

there are tshirts and posters. also you can donate directly to the project.

you're right on quite a few things, but bhyve is no where near production quality -- alpha at best. and openbsd has a wider and stronger support of wifi cards.

you mind doing some traceroutes to 4.2.2.2 and 8.8.8.8 just out of curiosity? :)

telecom, in general, isn't filled with the brightest of bulbs. especially in decision-making places...

Syntax changes and freebsds smp "enhancements" means you'll be waiting a bit longer, methinks

the PF available on FreeBSD is woefully out of date. If you use FreeBSD regularly and don't mess with pf, learn ipfw. it is quite powerful and much more performant.

I'm wondering what the chances of any other BSD being supported are...? Dragonfly? Open? ...Net? :)

edit: after actually reading TFA, it seems unlikely. Well, it seems like Dragonfly is most likely, if any others.

what will you do with a pfSense VM on DO?

Xen was originally implemented in NetBSD! NetBSD was the first dom0

interesting. I'd like to see performance comparisons to TCP/NC and/or CTCP.

cheap for one server...definitely not cheap at AWS scale.

bespoke network equipment and associated software stacks are what everything in the datacenter, and hopefully in the office/home, will be running in the next five years.

your statement ignores nearly a century of history and a bunch of technological facts.

oof. I want my routing protocol back.

you are getting "market familiarity" meaning they aren't beholden to you or your "crank" operating system and any schmo with a CC can bilk/bill them for support.

I missed the switchd/proprietary ASIC part. oops!

but is it faster than VALE/netgraph?