Well some did try to ban the sales of inefficient (incandescent) light bulbs a few years ago and you see how some of the yahoos railed against that as anti-free-market.
You do know that you can use the SAN environment variable to create UCC certs without having to modify openssl.cnf right? Its much easier to create multiple UCC certs that way.
GCC in the FreeBSD base is stuck at v4.2.1 as that was the last version licensed under the GPLv2. As this is about 7 years old by GCC standards a newer compiler is a welcomed change and since CLANG is BSD-licensed it is more in line with the project's goals anyway.
You try being followed by a stranger late at night in your neighborhood and see if you don't feel even the slightest bit provoked or concerned. Zimmerman followed when he shouldn't have and now someone's dead because of it.
Anybody who wasn't already assuming that all networked devices for which you haven't personally reviewed all the source code are anything other than hostile network actors has way too much time on their hands.
It would be more constructive to use whatever energy needed to pressure legacy IPv4 holders to give-up their space to start planning a move to v6 or at least a dual-stack architecture. This is like people complaining there's still momentum left in the cassette tape when CDs have been around for years. Postponing the inevitable doesn't stop the inevitable from happening.
Not a answer to your question per se, but I ran into a very similar problem when I moved to a new apartment 2 years ago. Rather than upgrade everything to 802.11n (and suffer the whole issue of too many wireless cooks in the pot as everyone now has their own access point) I got two Homeplug v2 adapters and moved my router to my office. Cable modem connects to my coax, which is then plugged into a Homeplug. The 2nd Homeplug then goes to the WAN interface on my house router. Works like a charm and I can still use wired connections for all my workstations.
Just a thought. I would have considered the 802.11n route but there's way too much activity in my area to make that feasible for 8+ machines (my 802.11g access point does work well for the 2-3 wireless devices I use regularly though, especially now that my access point is in my office and spaced further away from my neighbors' APs).
To be fair, it isn't mentioned anywhere in the pamphlet you receive with the iPhone or iPod, its buried within the iTunes website terms-and-conditions (at least last time I checked). If there were a warning label you had to pull-off each new iDevice I'd be right there with you, but you really have to look for it to find the iTunes lockout timeout (at least you did before this story broke).
That being said I'm generally not a believer of ignorance-as-a-defense, but I can certainly see why Apple would change this behavior and why the FTC would look into it.
VoIP over mobile is an entirely different beast than VoIP over wireline. The OP is right, there's a lot of kinks to be worked-out yet, particularly surrounding jitter/bufferbloat.
Slashdot Mirror
Just call the vomit-inducing situation a "feature" and be done with it. In fact, I can see this ushering in a whole new wave of quick-weight-loss VR!
No innovation? There's nothing else like them in the market.
Because the market left that space years ago...
...provide an experience very much like the desktop...
Excellent! I always wanted my phone to BSOD in the middle of an important call!
Well some did try to ban the sales of inefficient (incandescent) light bulbs a few years ago and you see how some of the yahoos railed against that as anti-free-market.
Uh, Big Business is doing a fantastic job of destroying the middle-class without the EPA even being involved.
You do know that you can use the SAN environment variable to create UCC certs without having to modify openssl.cnf right? Its much easier to create multiple UCC certs that way.
Hell, I still think the FCC counts it as high-speed even now in their broadband reports.
Licensing.
GCC in the FreeBSD base is stuck at v4.2.1 as that was the last version licensed under the GPLv2. As this is about 7 years old by GCC standards a newer compiler is a welcomed change and since CLANG is BSD-licensed it is more in line with the project's goals anyway.
You try being followed by a stranger late at night in your neighborhood and see if you don't feel even the slightest bit provoked or concerned. Zimmerman followed when he shouldn't have and now someone's dead because of it.
Sync directly with the bloatware and usability mess that is iTunes?
(note that some consider this a significant benefit)
Seconded, Zabbix with the ZAX Android client works very well in my setup here (sometimes too well, I hate getting alerts at 3am).
Should be the last FRIDAY in July
Anybody who wasn't already assuming that all networked devices for which you haven't personally reviewed all the source code are anything other than hostile network actors has way too much time on their hands.
FTFY^2
I'll describe the entire Earth in only 2:
Mostly Harmless
Now all EA games will come with free misery AND a Force Choke...
...only if you preorder at Gamestop
When no one's using the platform of course its going to be faster than the competition when shared resources are concerned.
impeachment yes, assassination no
wow, site goes down right as its being discussed....
If you're relying on RAs or DHCPv6 for server networks then you have bigger problems, not unlike rogue DHCP servers in IPv4.
It would be more constructive to use whatever energy needed to pressure legacy IPv4 holders to give-up their space to start planning a move to v6 or at least a dual-stack architecture. This is like people complaining there's still momentum left in the cassette tape when CDs have been around for years. Postponing the inevitable doesn't stop the inevitable from happening.
already done my friend
Not a answer to your question per se, but I ran into a very similar problem when I moved to a new apartment 2 years ago. Rather than upgrade everything to 802.11n (and suffer the whole issue of too many wireless cooks in the pot as everyone now has their own access point) I got two Homeplug v2 adapters and moved my router to my office. Cable modem connects to my coax, which is then plugged into a Homeplug. The 2nd Homeplug then goes to the WAN interface on my house router. Works like a charm and I can still use wired connections for all my workstations.
Just a thought. I would have considered the 802.11n route but there's way too much activity in my area to make that feasible for 8+ machines (my 802.11g access point does work well for the 2-3 wireless devices I use regularly though, especially now that my access point is in my office and spaced further away from my neighbors' APs).
To be fair, it isn't mentioned anywhere in the pamphlet you receive with the iPhone or iPod, its buried within the iTunes website terms-and-conditions (at least last time I checked). If there were a warning label you had to pull-off each new iDevice I'd be right there with you, but you really have to look for it to find the iTunes lockout timeout (at least you did before this story broke).
That being said I'm generally not a believer of ignorance-as-a-defense, but I can certainly see why Apple would change this behavior and why the FTC would look into it.
No its not, its providing an ALTERNATIVE to what might become bad behavior.
VoIP over mobile is an entirely different beast than VoIP over wireline. The OP is right, there's a lot of kinks to be worked-out yet, particularly surrounding jitter/bufferbloat.