UPkeep? Have you looked at upkeep of thin clients? Many are Embedded Windows XP. They still need firmware updates, configuration management, security management and more. And if you don't have to tools to update them all at once, you have to walk around to each one. It _doubles_ the number of O/S instances you have to manage. You still have to deploy apps to the VMs in the server farm (one per person), make sure Windows Updates get installed, A/V is up to date, etc. And then look at the cost of the thin clients - a full PC isn't much more these days.
The airbus that flew into the trees was caused by a pilot hot-dogging for the crowd. He wasn't supposed to fly that low or slow to begin with, and what he was doing was outside his experience. He had let the engines spool way down, almost to idle, and was flying very slow, almost at stall speed, and when he realized he needed thrust, it was too late for the engines to spool back up. He got way behind the plane, to put it simply. It was different than landing and then deciding to go around, they usually don't use so little thrust on when landing.
It was compounded by the plane not giving him as much feedback as it should for such a slow speed. You can see the control surfaces working hard to control the airplane, but there was little feedback to the pilot that the plane was working hard.
The engines behaved as expected - at the thrust setting he was using, the spool up time to full thrust is 30-40 seconds, and if you look at the video, he didnt have anywhere near that amount of time.
There is a difference between a business deciding it doesn't want one specific customers business, and Comcast, which is most locations a government protected monopoly, messing with traffic is pretty much is mandated to carry.
Businesses always have the ability to refuse customers, as long as it doesn't break any laws. And I have seen no suggestion that PIE or anyone else who has refused their business is breaking any laws.
Comcast was not providing what their "contract" said it should, and got caught.
You think they have full traceback? Ever looked at how skypeout works? Or how dialout on a ISDN PRI works?
You don't get valid caller ID. You have to be in the loop to see the real time SS7 information, and then still have to get someone to translate the IP Address to a physical location. Oops, its a coffee house WiFi network. Sorry, we don't know who called.
And that is just in the U.S. What about international calls? Think caller ID is reliable there?
If they get what they want for the Internet, it will be far more than they have now for telephones.
Get a used Thinkpad x31 or x32, or some other small/light "road warrior" laptop. If he is always connecting it to a projector, ditch the battery and anything else removable to reduce weight.
If all the neighbors are nice, run a 1000base-LX link. Get a couple of media converters, and you have 10km worth of distance available. Just be sure to get any grounding correct so a lightning strike at one end doesn't fry everything at the other end (some direct burial fiber has metallic cores for strength).
You can't encrypt IP Addresses, or the to: in email. You can try to send it through proxies, but if they have all the traffic info, or even just a large part of it, they still can analyze what kinds of web sites you visit and who you send and receive email from.
It's called traffic analysis, and that is exactly what they want to do.
I wish I got a percentage on the disk storage they will be purchasing.
That article isn't much more than links to other articles. Stangely seems like macro programming or a string of procedure calls. Nothing much new in the outer block - all the work was done before when the macros were written.
The machine i am writing this on is my main PC, and it has been running the same install of windows XP since i built it in december 2004. Windows generally won't screw up if you don't let it get infected and don't install broken software. The single biggest cause of reloading i have seen at work is from busted supposedly industrial strength anti-virus software going beserk and then not being able to uninstall itself. Something like AV software that digs deep into the O/S and then fails isn't the O/S's fault, at least not by itself.
A Philippine Air Lines 737 had it's center fuel tank explode ON THE GROUND while being pushed back in 1990 (years before TWA 800). The tank did not have much fuel in it, and there was bad wiring.
A Thai 727 also had a tank explosion sometime after TWA 800, that resulted in an AD.
I wouldn't be surprised if the time of day, the length of time ports are open and transferring, and what servers are being accessed are part of the equation. update.microsoft.com and anything on akami for instance probably don't count as much against the limit as much as transferrs to end users. And they can tell end uses because the dhcp ranges for the big networks (cable, dsl) are known for the most part.
Because unless both sides are right, which is unlikely, it means one side is wrong, and doesn't know how to code in very basic ways. Which is why so much software fails.
Each time there is a discussion on the mainframe, it shows how little many of the "PC" people know about other environments, and how little they are willing to listen about other environments.
The non-portatble software argument is rubbish. With how much these machines cost, they would port the software to other hardware if the other hardware really worked better or cost less. Many of these companies have $100M IT budgets o rmore - you don't think they can port their own software if they wanted to?
Massive loss of bags? Reference please. And define what you mean by "massive".
A simple web search finds data that shows the best airlines in Europe lose 0.4%, and the worst is %1.9. Considering the number of bags they handle, and how much they vary in size, shape, and destination most airlines do pretty well.
Buy or rent a power quality monitor, such as those from Dranetz. You probably will find your power isn't as clean as you thought, or your building is wired wrong.
Slashdot Mirror
UPkeep? Have you looked at upkeep of thin clients? Many are Embedded Windows XP. They still need firmware updates, configuration management, security management and more. And if you don't have to tools to update them all at once, you have to walk around to each one. It _doubles_ the number of O/S instances you have to manage. You still have to deploy apps to the VMs in the server farm (one per person), make sure Windows Updates get installed, A/V is up to date, etc. And then look at the cost of the thin clients - a full PC isn't much more these days.
The airbus that flew into the trees was caused by a pilot hot-dogging for the crowd. He wasn't supposed to fly that low or slow to begin with, and what he was doing was outside his experience. He had let the engines spool way down, almost to idle, and was flying very slow, almost at stall speed, and when he realized he needed thrust, it was too late for the engines to spool back up. He got way behind the plane, to put it simply. It was different than landing and then deciding to go around, they usually don't use so little thrust on when landing.
It was compounded by the plane not giving him as much feedback as it should for such a slow speed. You can see the control surfaces working hard to control the airplane, but there was little feedback to the pilot that the plane was working hard.
The engines behaved as expected - at the thrust setting he was using, the spool up time to full thrust is 30-40 seconds, and if you look at the video, he didnt have anywhere near that amount of time.
There is a difference between a business deciding it doesn't want one specific customers business, and Comcast, which is most locations a government protected monopoly, messing with traffic is pretty much is mandated to carry.
Businesses always have the ability to refuse customers, as long as it doesn't break any laws. And I have seen no suggestion that PIE or anyone else who has refused their business is breaking any laws.
Comcast was not providing what their "contract" said it should, and got caught.
You think they have full traceback? Ever looked at how skypeout works? Or how dialout on a ISDN PRI works?
You don't get valid caller ID. You have to be in the loop to see the real time SS7 information, and then still have to get someone to translate the IP Address to a physical location. Oops, its a coffee house WiFi network. Sorry, we don't know who called.
And that is just in the U.S. What about international calls? Think caller ID is reliable there?
If they get what they want for the Internet, it will be far more than they have now for telephones.
Give me a break. They should have a way to do everyone at once, what happens when they all get union negotiated or legislated raises?
Also, it's not the fault of COBOL. It is the fault of an inflexible system, and that can be screwed up in any language, even English!
Get a used Thinkpad x31 or x32, or some other small/light "road warrior" laptop. If he is always connecting it to a projector, ditch the battery and anything else removable to reduce weight.
Or something like that.
It's for Super Audio CD, and the cable carries a bitstream that doesn't have much or any error correction.
If all the neighbors are nice, run a 1000base-LX link. Get a couple of media converters, and you have 10km worth of distance available. Just be sure to get any grounding correct so a lightning strike at one end doesn't fry everything at the other end (some direct burial fiber has metallic cores for strength).
You can't encrypt IP Addresses, or the to: in email. You can try to send it through proxies, but if they have all the traffic info, or even just a large part of it, they still can analyze what kinds of web sites you visit and who you send and receive email from.
It's called traffic analysis, and that is exactly what they want to do.
I wish I got a percentage on the disk storage they will be purchasing.
We wouldn't tolerate an interruption to roads? Then what is your response to the emergency multi-day closure of I-95 in Philadelphia?
http://ap.google.com/article/ALeqM5hZVC3hXyVXkw7fYNFMJKI5V4BCHQD8VFTA200
That article isn't much more than links to other articles. Stangely seems like macro programming or a string of procedure calls. Nothing much new in the outer block - all the work was done before when the macros were written.
The machine i am writing this on is my main PC, and it has been running the same install of windows XP since i built it in december 2004. Windows generally won't screw up if you don't let it get infected and don't install broken software. The single biggest cause of reloading i have seen at work is from busted supposedly industrial strength anti-virus software going beserk and then not being able to uninstall itself. Something like AV software that digs deep into the O/S and then fails isn't the O/S's fault, at least not by itself.
A Philippine Air Lines 737 had it's center fuel tank explode ON THE GROUND while being pushed back in 1990 (years before TWA 800). The tank did not have much fuel in it, and there was bad wiring.
A Thai 727 also had a tank explosion sometime after TWA 800, that resulted in an AD.
Modern airliners have exploded on their own.
It stopped being just "their network" when they signed agreements with local governments for access to public rights-of-way.
I wouldn't be surprised if the time of day, the length of time ports are open and transferring, and what servers are being accessed are part of the equation. update.microsoft.com and anything on akami for instance probably don't count as much against the limit as much as transferrs to end users. And they can tell end uses because the dhcp ranges for the big networks (cable, dsl) are known for the most part.
Skype uses so little bandwith (50kbps?) that it would never reach a cap that is in the 10s of GB.
Because unless both sides are right, which is unlikely, it means one side is wrong, and doesn't know how to code in very basic ways. Which is why so much software fails.
Once you try it, you will never go back
Each time there is a discussion on the mainframe, it shows how little many of the "PC" people know about other environments, and how little they are willing to listen about other environments.
The non-portatble software argument is rubbish. With how much these machines cost, they would port the software to other hardware if the other hardware really worked better or cost less. Many of these companies have $100M IT budgets o rmore - you don't think they can port their own software if they wanted to?
6.28 mishandled bags per 1000 passengers.
h tml/dot083_06.html
:-)
http://www.bts.gov/press_releases/2006/dot083_06/
Thats mishandled, not lost.
When I see articles about software development groups happy to get 10bugs/KLOC, baggage handlers aren't doing bad
Massive loss of bags? Reference please. And define what you mean by "massive".
A simple web search finds data that shows the best airlines in Europe lose 0.4%, and the worst is %1.9. Considering the number of bags they handle, and how much they vary in size, shape, and destination most airlines do pretty well.
Buy or rent a power quality monitor, such as those from Dranetz. You probably will find your power isn't as clean as you thought, or your building is wired wrong.
Been using sparco and cdw for years. both deliver, and sparcos live availability by warehouse helps knowing when they can get it to you.