Agreed. Many of us are still using rigs from the 90's, some from the earliest days of SSB. These rigs don't necessarily support digital modes.
What do you mean, "not necessarily"? I just set up FreeDV and made a contact with a friend using an old PC I have for logging and runnign fldigi and a Yaesu FT-101EE from 1976. Worked just fine.
I've had it for almost 2 years and 20,000 miles and it has been flawless.
That's an amazingly low bar.
I'm not saying I think it will be problematic, but 2 years/20k miles of problem free motoring is pretty much a useless statistic in this day and age.
You can get several full autos for well under $8k, a sum of money most people have spent considerably more than for their vehicle.
Most people who spend that kind of money on a car do so over time through financed loans rather than a lump sum. I'm not aware of any bank that will give out assault-rifle loans.
What the hell does that have to do with anything relative to "average citizens" having access to them.
Also, someone who finances an $8,000 car has some serious financial issues and probably should not be spending $8k on a car.
The last place I researched you had to get the chief of police to sign off on each and every one
You register them to a trust and there is no signoff.
Like everything else, its about knowing the process. None of this is difficult (for most) to figure out.
I said nothing at all about cost, as I don't see the relevance. You can get several full autos for well under $8k, a sum of money most people have spent considerably more than for their vehicle. In the grand scheme of things, that's not a lot of money. For a weapon? Yes. But it's something most people would be able to put together should they want or need to.
Your average citizen cannot purchase an assault rifle.
Since when? Almost every state allows it.
All you have to do is submit your paperwork and $200 for the tax stamp to the ATF and wait a month or so.
Equipment is probably the reason the carriers don't.
Yes, like I said "most of your non commodity equipment". While I could set up signaling with IPv6 using OpenSIPs or similar, the idea of running a bi-lat with a major carrier that way is laughable. Not to mention the fact that you'll pretty much have to B2BUA traffic going from v6 to v4 (since none of your other carriers support v6) or it will be an even bigger support nightmare. And as far as support nightmares go......none of the packet capture and analysis tools commonly used support v6.
VoIP (real carrier voip.....not you nerds with an Asterisk box in your house) is a long way away from being v6 ready.
And what about the cost of supporting an entirely different operating system? To have to train and pay for a linux-educated support staff surely represents an additional cost.
That's hilarious. For business support, they already have those people in the server division. For home or small business sales the people aren't trained anyway: it's just another call center script/q&a that needs to be written and sent to India.
I always wondered why the ISP I worked at could just be handed a
They weren't. AS numbers cost money, as do IP allocations.
at which point it no longer matters what ISP you are using.
Did I miss that part where home routers are all running BGP now?
Not everything works with IPv6 yet. Most stuff does, but most organizations still have some stuff that doesn't quite yet.
That list is ridiculously short. Even my half decade old brother laser printer supports ipv6. The only barrier at this time in "my organization" is my openafs fileserver cluster doesn't support ipv6. Other than that...
Unless you work in VoIP. Then then that list is "most of your non-commodity equipment and none of your carriers."
And you're sure that they had everything that should have been redundant actually setup as required to work in AWS? Or did they just have redundant db and webservers but some stupid master index that everything has to pass through running in a single zone? 9/10 that is the problem. People can justify multiple dbs because of performance and data integrity needs. People justify multiple webservers so that they can get low lantency to different areas of the globe and under load. Then someone throws on top a cassandra or memcache layer or whatever and plays with it in one zone
I'm not sure what that has to do with a cheap bastard with a $30 a month setup, as I was replying to in your post. But I'll play along: of course I can't be sure of any of those things. But I'm having a hard time a marquee customer of that size is doing things that wrong. The reports of other availability zones being affected/degraded seems to bare this out.
Ah, ok - thanks, I managed to miss that. Most of our servers are still on RHEL 5 because of some odd issues we've experienced with LDAP under RHEL 6.
Because goddamn sudoers doesn't work with LDAP since 6.1, when it used to work just fine in 6.0 and now nslcd pukes on the config you need?
Yeah....this is FINALLY patched in 6.3 (a week ago or so). Be aware that you need to change some things and add an additional conf file to make it work. What a pain in the ass, but it's finally over (or will be for me once CentOS gets it downstream).
https://bugzilla.redhat.com/show_bug.cgi?id=760843
Is your job running? You'd better go catch it!
