Wow, an impossible problem to solve! Nobody who writes programs has ever installed their own wireless radio before? Drills and cat5 crimpers are beyond you, eh?
"Wireless is so exorbitant if I want to live here I have to have Comcast and they won't come!! I have to take a huge loss right now just to stay in business!!" -- Said some fucking idiot
Hah! Getting a "fair" criminal trial can be a very expensive proposition in the US. That's for a normal person. For Snowden, in the current political climate, seriously????? He's fucked. No amount of guarantees will un-fuck him.
Quite the opposite, in fact, now Verizon can eventually likely get more funding to serve areas that are not profitable by themselves (or not profitable in a short enough time frame).
That's because you're an idiot. ksh and bash both tell you how this works. It's far from rocket science here.
The funny thing about "FreeBSD's PF is essentially an actively maintained fork which doesn't follow the upstream closely anymore" is that, on a Soekris net6501, PF is all-around faster with OpenBSD 5.7-beta (current snapshots) on a SINGLE core than FreeBSD PF is on multiple cores.
oh really? you mean the many years after the early realtek chip was maligned, still avoid them?
You'll have to explain why they're crap.
I assume you've used it? because it keeps time on my servers and serves that time to well over 10k devices on my network!
It sets your local server time immediately if you use -s. Otherwise, it slowly drifts your local clock to the real time, which could take days if it is far off. I always use ntpd -s on boot for systems with no RTC. Or ntpd -s when my clock is way off. The drift feature is designed to keep software from freaking out due to sudden time changes.
Please enlighten us.
It would be nice if the whole world got the BCP38 memo. But they haven't. I'm a network operator. I got off my lazy ass and firewalled all of the ntp.org servers on my network, that customers didn't enable and had no idea were even running, courtesy of Cisco and various Linux distributions. Reality is a bitch.
Admit it. It's a large, fat piece of shit that nobody should be running. OpenNTPD in fact works perfectly as an accurate NTP (not SNTP) server AND client for more than 10,000 devices on my network.
Funny how I am firewalling ports so that your vulnerable shit running on customer Cisco firewalls, Linux servers and other customer boxes across my network, just so that your shit doesn't cause a 550x amplification factor, or who knows whatever other vulnerabilities compromise these devices. My hat is off to you for your shit garbage. Fuck you, sir.
This is moronic.
A very high percentage of people use ntp simply because they want accurate time on their devices.
Why should they use a program that does 90% something else (by your estimation) as a piece of critical infrastructure running on all of their devices?
OpenNTPD allows me to serve accurate time to devices across my network, and it allows those devices to keep their local clock set right as well.
If I was you, I guess I should feel bad I'm missing 90% of the features, like buffer overflows and other security failures in the ntp.org version!!! But, I don't. I'm not a fucking moron.
You might have mail.