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.
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.
And I think you're missing the point that you can buy EVERY part, already assembled, face to face between a private buyer and seller with no background check. 100% legally in most states.
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.
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... then goes live... in one zone. Opps.
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).
Hmm no you don't usually have much control over the recovery either. I was involved in a outage once because some guys trenching cable cut clean through our fiber bundle. There is no controlling anything that happens after that you are just down until the fiber is repaired.
Diverse utility paths are pretty much required for any datacenter. And even that may not be enough, which I will respond to in the next point.
In a cloud environment, given that you have a DR plan you press a button and you are back online.
Two things: that whole concept is not a "cloud environment" thing, it's the way things have been done for a long time. Also, if you have to "press a button" (or perform any action) you are doing it pretty much wrong and have nothing to be smug about.
None of this is magic, not unique to "cloud computing". Stop letting your brain fall out of your ear when you hear the latest buzz words. "Cloud computing" is code for "we figured out how to lease you a fractional part of several servers and call it something else". The only part about it that is new is the marketing. It's carries all the same risks as it did before, but now has some more tools, platform support and vendors due to its trendiness and the increased needs for the types of service in the general market area it covers.
No, I'm not working my first or second job in the industry. That's why I know "THE CLOUD! THE CLOUD!" is not the answer to all problems. It's just another tool that can be used appropriately or inappropriately. Much of what I've seen lately has been inappropriate, but wholly in keeping with what the marcom firms the providers have hired are messaging. Sounds like you've bought into that too. I'd suggest you get some perspective on the industry you are presumably a part of.
I think most are just cheap bastards that are upset that their one server $30/month setup didn't by a redundant datacentre and that opps maybe they should have listened went people said that geo-redundancy: "It's a good thing" TM.
Yeah....Netflix is totally one of those places. Oh...wait....no they aren't and they were down anyway.
I wonder how many more of these it takes before the cloud-skeptics start winning the debates with management a lot more often.
This sort of thing never ever happens when you host everything in-house?
Obviously they do. But at least you have some control over the recovery, rather than sitting around watching for carefully-worded email and Twitter updates from Amazon about when you just might get access to the shit you are paying for again. That makes communicating real information to your customers a bit easier.
Of course, you can always use the excuse that it's not your fault and blame Amazon ("see...look at all the other people who are down"). But that's largely a marketing decision I suppose.
"Several times and for multiple businesses. Have you?"
I'd actually be interesting in hearing your analysis and experience. I'm looking at this myself and finding that cost advantages differ depending on scenario - there just doesn't seem to be a clear cut point at which one solution costs less than the other for all but the most trivial scenarios.
Because it really depends on the business and the application. It also depends on how much bandwidth you use and if you have geographical limitations which would make accessing that bandwidth more costly in one or more locations.
If you are in it for the long haul, why not have control over your own cheap commodity machines and "scale into the cloud" for overages until you acquire more hardware? Then you can actually hav control of those little things that let you switch between datacenters easily like.....you know, your BGP and other trivial things like that.
There's definitely no one sized fits all for this, but the bulk of the statrups I see that are cloud based appear to be 1.) a bunch of developers first and foremost, so not data center or network engineers at all and 2.) not capitalized well enough in the beginning to be able to afford leasing and equipping space in multiple data centers. And there's nothing at all wrong with that. It's a valid choice if you recognize the reality of what you are buying rather than believing the marketing hype hook line and sinker.
Law will net you/much/ more money for your effort?
This right here proves you are 100% clueless and talking out of your ass. Post law school employment is absolutely PATHETIC right now. It's at something like 55%.
Moderate level intelligence go where the money is. Hence the jump in low skill computing ability in 97-00
Spoken like someone else who lived through it. What a horrible time to be hiring high end network engineers or anything else computer related......the amount of crap resumes was simply astounding. Everyone was a 6-month-old CNE.
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.
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.
Does any of this make it so an "average citizen" can't buy one?
Answer: no. That was the point of my post.
I'm using the correct definition: an intermediate caliber magazine fed automatic rifle designed for infantry use.
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.
And I think you're missing the point that you can buy EVERY part, already assembled, face to face between a private buyer and seller with no background check. 100% legally in most states.
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 /16 for free .
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 ... then goes live ... in one zone. Opps.
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
Hmm no you don't usually have much control over the recovery either. I was involved in a outage once because some guys trenching cable cut clean through our fiber bundle. There is no controlling anything that happens after that you are just down until the fiber is repaired.
Diverse utility paths are pretty much required for any datacenter. And even that may not be enough, which I will respond to in the next point.
In a cloud environment, given that you have a DR plan you press a button and you are back online.
Two things: that whole concept is not a "cloud environment" thing, it's the way things have been done for a long time. Also, if you have to "press a button" (or perform any action) you are doing it pretty much wrong and have nothing to be smug about. None of this is magic, not unique to "cloud computing". Stop letting your brain fall out of your ear when you hear the latest buzz words. "Cloud computing" is code for "we figured out how to lease you a fractional part of several servers and call it something else". The only part about it that is new is the marketing. It's carries all the same risks as it did before, but now has some more tools, platform support and vendors due to its trendiness and the increased needs for the types of service in the general market area it covers.
No, I'm not working my first or second job in the industry. That's why I know "THE CLOUD! THE CLOUD!" is not the answer to all problems. It's just another tool that can be used appropriately or inappropriately. Much of what I've seen lately has been inappropriate, but wholly in keeping with what the marcom firms the providers have hired are messaging. Sounds like you've bought into that too. I'd suggest you get some perspective on the industry you are presumably a part of.
I think most are just cheap bastards that are upset that their one server $30/month setup didn't by a redundant datacentre and that opps maybe they should have listened went people said that geo-redundancy: "It's a good thing" TM.
Yeah....Netflix is totally one of those places. Oh...wait....no they aren't and they were down anyway.
I wonder how many more of these it takes before the cloud-skeptics start winning the debates with management a lot more often.
This sort of thing never ever happens when you host everything in-house?
Obviously they do. But at least you have some control over the recovery, rather than sitting around watching for carefully-worded email and Twitter updates from Amazon about when you just might get access to the shit you are paying for again. That makes communicating real information to your customers a bit easier.
Of course, you can always use the excuse that it's not your fault and blame Amazon ("see...look at all the other people who are down"). But that's largely a marketing decision I suppose.
"Several times and for multiple businesses. Have you?"
I'd actually be interesting in hearing your analysis and experience. I'm looking at this myself and finding that cost advantages differ depending on scenario - there just doesn't seem to be a clear cut point at which one solution costs less than the other for all but the most trivial scenarios.
Because it really depends on the business and the application. It also depends on how much bandwidth you use and if you have geographical limitations which would make accessing that bandwidth more costly in one or more locations.
If you are in it for the long haul, why not have control over your own cheap commodity machines and "scale into the cloud" for overages until you acquire more hardware? Then you can actually hav control of those little things that let you switch between datacenters easily like.....you know, your BGP and other trivial things like that.
There's definitely no one sized fits all for this, but the bulk of the statrups I see that are cloud based appear to be 1.) a bunch of developers first and foremost, so not data center or network engineers at all and 2.) not capitalized well enough in the beginning to be able to afford leasing and equipping space in multiple data centers. And there's nothing at all wrong with that. It's a valid choice if you recognize the reality of what you are buying rather than believing the marketing hype hook line and sinker.
mod_php the Apache module.
As much as I try, I can only get mod_php to load in a web server. My browsers don't seem to know quite what to do with it.
No foreign keys with NDB
Also correct. Your point? Other than that specific tools were made for specific jobs.
It seems to me that MySQL can also be run in memory. Apparently that's how the clustered database works (or used to work).
Absolutely correct. NDB Cluster. It's quite fast, even on older hardware providing you have enough RAM to hold your database.
Law will net you /much/ more money for your effort?
This right here proves you are 100% clueless and talking out of your ass. Post law school employment is absolutely PATHETIC right now. It's at something like 55%.
Moderate level intelligence go where the money is. Hence the jump in low skill computing ability in 97-00
Spoken like someone else who lived through it. What a horrible time to be hiring high end network engineers or anything else computer related......the amount of crap resumes was simply astounding. Everyone was a 6-month-old CNE.
instant water heaters
You need to do a lot more research before spewing things like this. And I'm only quoting the juiciest part.