It would not cause a violent decompression, merely a leak. The outflow valve at the back of the fuselage would just close slightly as a consequence. An airliner's pressurization system can easily cope with some bullet holes.
I think Yahoo! realise that Ballmer really, really, really wants to buy them - after all, it eliminates an open source competitor. Therefore, they are betting they have Ballmer over a barrel, and can name any silly price they care to name - because Microsoft is desperate to buy them.
Just because some talking head waffles on about how Zimbra going away will hurt Linux (it won't), it doesn't mean that the development model is broken. Kernel development is doing just fine.
Since Firefox works on Windows too, it's like saying any possible Firefox trouble hurts Windows. It doesn't.
That's already done pretty much everywhere! Severe weather, or a major accident on a highway? Guess what - you're often advised to "only use that road for journeys that are extremely necessary".
They aren't telling home users to get stuffed, they are requesting that they limit their internet access to stuff that's essential until the problem is fixed.
I own a house. I don't have to mow any damn lawns - I don't have one. I removed the lawn, put in a pond, and used stone chippings instead of grass and planted some palms.
Unlike renting, my mortgage doesn't go up every year. So in real terms, my housing costs fall every year. Within a few years my mortgage will be less than the rent on a 1 bed apartment.
Google isn't set up with the intent to facilitate copyright infringement. The Pirate Bay, by contrast, is explicitly set up to facilitate copyright infringement, and not only that - they boast about it.
The law will treat different people differently depending on intent. For example, if you accidentally kill someone you don't get charged with murder - indeed, you may not face any punishment at all if it is a genuine accident and you weren't egregiously negligent. However, if you deliberately kill someone you go to jail for a long time. Intent. That's the key difference.
Google and the ISPs don't have their networks set up with the intent to facilitate piracy. Indeed, send a DMCA takedown to Google and they will comply. The Pirate Bay on the other hand very much intends to facilitate copyright infringement; send them a takedown notice and they mock you.
Because, well, there are so many bad PHP applications. My original post did not single out PHP, it singled out bad PHP _applications_. PHPbb and PHPnuke are well known examples - serious flaws found in both, and unpatched versions of this PHP software is left lying around for years.
The typical shared hosting only offers PHP as a scripting language. So lots of non-administrators and non-developers are uploading random PHP scripts to their $2 a month hosting sites, and then not updating them when security vulnerabilities are found.
It doesn't help that many of the random tutorials on the web on PHP show examples of sending things like unchecked values to SQL select statements and unchecked values used to open files on the filesystem.
Just as you can make Windows secure, the vast majority of Windows users are the infection vector (rather than Windows itself) because they install random crap and don't update it. Same for PHP - its ubiquity on cheap shared hosting means lots of badly written random PHP crap floats around, and these almost unsupervised servers end up getting rooted via a PHP script and a local root exploit.
I *do* run PHP stuff on my servers - such as MediaWiki. But I keep them up to date. For everyone who keeps their scripts up to date, there are 10 shared hosting accounts which don't.
Symantec probably don't pay, they probably just have a cross-licensing agreement. Getting a cross-licensing agreement in place is probably a whole lot less effort than litigating - so the companies choose the path of least resistance.
Schools are supposed to be educating, not training people to click on widgets like monkeys.
Someone who knows the general concepts will find they easily transfer to Windows or Mac OS X. GUI driven operating systems all work pretty much the same way. Writing a document in OpenOffice isn't appreciably different than in MS Office. The concepts are exactly the same, only the widgets are slightly different.
Linux is the best method of doing so because it will free up money that can go to paying teachers.
Your argument can easily go a stage further; for instance, since Microsoft occasionally completely change the GUI for MS Office, then surely if you've learned Office 2003, then your skills are totally useless for Office 2007? Not at all. And neither are skills learned using OpenOffice useless when using MS Office.
The article (and the site that sells it) are utterly useless and don't even give a spec on what the lamp actually is. From the video, when they turn the light off it dims down like a hot halogen light. I suspect it's just a halogen bulb rated at a couple of hundred watts - and it's just the heat of the bulb close up, rather than the actual light itself that's setting stuff on fire. A 300W halogen lamp will set things on fire that are close to it with ease, but only because the filament gets extremely hot and is kicking out enough IR to set things on fire that are right close to it.
If, by most organic material, they are talking about cellulosic ethanol, then no - they won't be using corn as the feed stock (well, they might use the stalks and other bits of chaff that's removed from the corn). Cellulosic ethanol can be made from any invasive weed - use poor agricultural land, and find anything that will grow invasively on it - switchgrass, hemp, bamboo etc., and you have a good feedstock.
It's quite possibly due to buggy PHP scripts. I've seen it before; what happens is the attacker goes for some unpatched vulnerability in PHPnuke, PHPbb or similar software. This gets them non-root access. They use this to 'wget some-hack.c' to the/tmp directory, build this hack then execute this to exploit a local root exploit.
This is why I treat all local root exploits as seriously as remote root exploits. All it takes is one buggy PHP script and then the attacker can try local root vulns.
Depends who you work for in IBM. I used to work for IBM, and my experience is a complete contrast to yours: the majority of people earned a 2, several earned a 1, only a few got a 3 and you could tell the people who were going to end up with a 3. Our immediate management was competent, and there was a good working relationship based on trust and respect. They treated me very well, for instance, when my mother unexpectedly became ill and died, I got to take off all the compassionate leave I needed (since she was thousands of miles away), on full pay, and not deducted from my vacation.
The only bad thing we had was that upper management tried to sneakily enforce 10% mandatory overtime by insisting one of your goals was a certain utilization rate, that on first blush was reasonable but if you examined it closely was only achievable by working at least 10% overtime all the time. My personnel manager told all of us with a wry smile on her face that if we didn't put it in my personal plan (I can't actually remember what these things were called, other than they had a Win-Execute-Team thing in them) then it wasn't a goal we had to meet, and upper management never checked the plans anyway; they were a bit out of touch. So I never put the utilization goal in. (I consistently was awarded a 1 on my review too).
The thing is I didn't mind doing a bit extra when it was required due to genuine unforseen circumstances, given that (apart from the out of touch upper management) we had a very good working relationship, and our immediate management were clueful enough to set reasonable schedules based on our input. Following the SEI CMM level 3 process also helped - we became very adept at sizing jobs such that they almost always took the amount of time that was forecast - this really reduced the overtime rate.
Virtual desktops have been around in Linux since 1992. The Open Look Virtual Window Manager had it. Prior to Linux, the Solbourne Window Manager (which predates Windows 3.0) had a virtual desktop.
Actually, it's not. Each device must be already programmed, and the flash memory will undoubtedly be in system programmable - that's probably how they get the MAC address on it in the first place. It would be just one additional value to write to have some kind of random ID and password. The firmware isn't an ASIC, it's bog standard trivially reprogrammable flash these days.
Just to get the message across to others, and correct the "prollyfuelexhaustion" tag, fuel exhaustion was immediately ruled out. A significant quantity of fuel leaked from the crashed plane.
No, that was ruled out immediately. A significant quantity of jet fuel leaked from the aircraft after the crash. One of the first announcements from the AAIB was that the aircraft had not run out of fuel. It's the first thing the investigators would have checked: is there fuel leaking? (yes) is there fuel in the unbreached tanks? (yes)
Running out of fuel has already been ruled out - it was ruled out within minutes. It leaked quite a lot of fuel from a breached fuel tank, and the first thing the investigators would have done would be check for fuel in other tanks as well - it's a simple check to make. They publically announced that fuel exhaustion had been ruled out within hours of the crash.
Fuel exhaustion was immediately ruled out - significant fuel leaked out at the crash site. Fuel exhaustion was one of the first things that was publically ruled out by the investigators - it's easy to rule out - look for leaked fuel, and check for fuel in tanks that haven't been breached.
This doesn't rule out fuel starvation - where for some reason, while there is plenty of fuel on board, it's not being delivered to the engines.
Also, redunant systems have a nasty habit of occasionally not being quite as redundant as the designer hoped. A recent example is the Boeing 747-400 (i.e. a late model 747, with all electronic instrumentation) which lost complete generator power, despite having 4 generators and independent power buses and an APU. The power was routed underneath the first class toilet - which blocked and overflowed. But it seems the 747 designers had thought of that eventuality, and had designed it with a tray under the toilets to ensure an overflow wouldn't go on something it shouldn't.
The tray was cracked. The water leaked right onto the equipment below, and the crew were left with nothing but battery power. Fortunately, they were not far from landing so battery power was sufficient, otherwise they may have had to go back to old fashioned celestial navigation.
There have been several incidents of modern airliners catching fire all by themselves. Fortunately, with the exception of TWA800 they have all been on the ground. But the conditions have been the same: stochiometric mixture of fuel vapour and air in a fuel tank, set off by an electrical fault.
I doubt the aircraft stalled: a large aircraft like a Boeing 777 will _not_ recover from a stall in 600 ft, and everyone would have been dead. If it stalled at all, it would have been just before touchdown while the crew were trying to arrest whatever sink rate they could before impact.
As for fuel exhaustion - that was ruled out very quickly - plenty of fuel leaked from at least one breached fuel tank. It's the first thing the investigators would have done - look in the tanks and see if there was fuel. That doesn't rule out fuel STARVATION though - you can have plenty of fuel on board, but something stopping it from reaching the engines.
Since this is the natural place for living room electronics: neatly installed in some under-TV cabinet, surely it behooves the manufacturer to design their equipment to live where many people are going to instinctively put them?
Slashdot Mirror
It would not cause a violent decompression, merely a leak. The outflow valve at the back of the fuselage would just close slightly as a consequence. An airliner's pressurization system can easily cope with some bullet holes.
I think Yahoo! realise that Ballmer really, really, really wants to buy them - after all, it eliminates an open source competitor. Therefore, they are betting they have Ballmer over a barrel, and can name any silly price they care to name - because Microsoft is desperate to buy them.
Fortunately, there's this brand new technology called DNS that makes the computer do it for you :-)
NAT is an ugly hack. It's like a telephone extension lead that only lets you make outgoing calls.
Dynamic IP addresses suck too, for that matter: it's like a phone that changes number every time you use it.
Firefox is not Linux
Just because some talking head waffles on about how Zimbra going away will hurt Linux (it won't), it doesn't mean that the development model is broken. Kernel development is doing just fine.
Since Firefox works on Windows too, it's like saying any possible Firefox trouble hurts Windows. It doesn't.
That's already done pretty much everywhere! Severe weather, or a major accident on a highway? Guess what - you're often advised to "only use that road for journeys that are extremely necessary".
They aren't telling home users to get stuffed, they are requesting that they limit their internet access to stuff that's essential until the problem is fixed.
I own a house. I don't have to mow any damn lawns - I don't have one. I removed the lawn, put in a pond, and used stone chippings instead of grass and planted some palms.
Unlike renting, my mortgage doesn't go up every year. So in real terms, my housing costs fall every year. Within a few years my mortgage will be less than the rent on a 1 bed apartment.
It's all about intent.
Google isn't set up with the intent to facilitate copyright infringement. The Pirate Bay, by contrast, is explicitly set up to facilitate copyright infringement, and not only that - they boast about it.
The law will treat different people differently depending on intent. For example, if you accidentally kill someone you don't get charged with murder - indeed, you may not face any punishment at all if it is a genuine accident and you weren't egregiously negligent. However, if you deliberately kill someone you go to jail for a long time. Intent. That's the key difference.
Google and the ISPs don't have their networks set up with the intent to facilitate piracy. Indeed, send a DMCA takedown to Google and they will comply. The Pirate Bay on the other hand very much intends to facilitate copyright infringement; send them a takedown notice and they mock you.
Because, well, there are so many bad PHP applications. My original post did not single out PHP, it singled out bad PHP _applications_. PHPbb and PHPnuke are well known examples - serious flaws found in both, and unpatched versions of this PHP software is left lying around for years.
The typical shared hosting only offers PHP as a scripting language. So lots of non-administrators and non-developers are uploading random PHP scripts to their $2 a month hosting sites, and then not updating them when security vulnerabilities are found.
It doesn't help that many of the random tutorials on the web on PHP show examples of sending things like unchecked values to SQL select statements and unchecked values used to open files on the filesystem.
Just as you can make Windows secure, the vast majority of Windows users are the infection vector (rather than Windows itself) because they install random crap and don't update it. Same for PHP - its ubiquity on cheap shared hosting means lots of badly written random PHP crap floats around, and these almost unsupervised servers end up getting rooted via a PHP script and a local root exploit.
I *do* run PHP stuff on my servers - such as MediaWiki. But I keep them up to date. For everyone who keeps their scripts up to date, there are 10 shared hosting accounts which don't.
Symantec probably don't pay, they probably just have a cross-licensing agreement. Getting a cross-licensing agreement in place is probably a whole lot less effort than litigating - so the companies choose the path of least resistance.
Schools are supposed to be educating, not training people to click on widgets like monkeys.
Someone who knows the general concepts will find they easily transfer to Windows or Mac OS X. GUI driven operating systems all work pretty much the same way. Writing a document in OpenOffice isn't appreciably different than in MS Office. The concepts are exactly the same, only the widgets are slightly different.
Linux is the best method of doing so because it will free up money that can go to paying teachers.
Your argument can easily go a stage further; for instance, since Microsoft occasionally completely change the GUI for MS Office, then surely if you've learned Office 2003, then your skills are totally useless for Office 2007? Not at all. And neither are skills learned using OpenOffice useless when using MS Office.
The article (and the site that sells it) are utterly useless and don't even give a spec on what the lamp actually is. From the video, when they turn the light off it dims down like a hot halogen light. I suspect it's just a halogen bulb rated at a couple of hundred watts - and it's just the heat of the bulb close up, rather than the actual light itself that's setting stuff on fire. A 300W halogen lamp will set things on fire that are close to it with ease, but only because the filament gets extremely hot and is kicking out enough IR to set things on fire that are right close to it.
If, by most organic material, they are talking about cellulosic ethanol, then no - they won't be using corn as the feed stock (well, they might use the stalks and other bits of chaff that's removed from the corn). Cellulosic ethanol can be made from any invasive weed - use poor agricultural land, and find anything that will grow invasively on it - switchgrass, hemp, bamboo etc., and you have a good feedstock.
It's quite possibly due to buggy PHP scripts. I've seen it before; what happens is the attacker goes for some unpatched vulnerability in PHPnuke, PHPbb or similar software. This gets them non-root access. They use this to 'wget some-hack.c' to the /tmp directory, build this hack then execute this to exploit a local root exploit.
This is why I treat all local root exploits as seriously as remote root exploits. All it takes is one buggy PHP script and then the attacker can try local root vulns.
Depends who you work for in IBM. I used to work for IBM, and my experience is a complete contrast to yours: the majority of people earned a 2, several earned a 1, only a few got a 3 and you could tell the people who were going to end up with a 3. Our immediate management was competent, and there was a good working relationship based on trust and respect. They treated me very well, for instance, when my mother unexpectedly became ill and died, I got to take off all the compassionate leave I needed (since she was thousands of miles away), on full pay, and not deducted from my vacation.
The only bad thing we had was that upper management tried to sneakily enforce 10% mandatory overtime by insisting one of your goals was a certain utilization rate, that on first blush was reasonable but if you examined it closely was only achievable by working at least 10% overtime all the time. My personnel manager told all of us with a wry smile on her face that if we didn't put it in my personal plan (I can't actually remember what these things were called, other than they had a Win-Execute-Team thing in them) then it wasn't a goal we had to meet, and upper management never checked the plans anyway; they were a bit out of touch. So I never put the utilization goal in. (I consistently was awarded a 1 on my review too).
The thing is I didn't mind doing a bit extra when it was required due to genuine unforseen circumstances, given that (apart from the out of touch upper management) we had a very good working relationship, and our immediate management were clueful enough to set reasonable schedules based on our input. Following the SEI CMM level 3 process also helped - we became very adept at sizing jobs such that they almost always took the amount of time that was forecast - this really reduced the overtime rate.
Virtual desktops have been around in Linux since 1992. The Open Look Virtual Window Manager had it. Prior to Linux, the Solbourne Window Manager (which predates Windows 3.0) had a virtual desktop.
Actually, it's not. Each device must be already programmed, and the flash memory will undoubtedly be in system programmable - that's probably how they get the MAC address on it in the first place. It would be just one additional value to write to have some kind of random ID and password. The firmware isn't an ASIC, it's bog standard trivially reprogrammable flash these days.
[reiser@home]~$ kill -9 %1 ./significant-other
[1]+ Killed
[reiser@home]~$ _
Just to get the message across to others, and correct the "prollyfuelexhaustion" tag, fuel exhaustion was immediately ruled out. A significant quantity of fuel leaked from the crashed plane.
The AAIB initial report is here:
http://www.aaib.dft.gov.uk/latest_news/accident__heathrow_17_january_2008___initial_report.cfm
No, that was ruled out immediately. A significant quantity of jet fuel leaked from the aircraft after the crash. One of the first announcements from the AAIB was that the aircraft had not run out of fuel. It's the first thing the investigators would have checked: is there fuel leaking? (yes) is there fuel in the unbreached tanks? (yes)
Running out of fuel has already been ruled out - it was ruled out within minutes. It leaked quite a lot of fuel from a breached fuel tank, and the first thing the investigators would have done would be check for fuel in other tanks as well - it's a simple check to make. They publically announced that fuel exhaustion had been ruled out within hours of the crash.
Fuel exhaustion was immediately ruled out - significant fuel leaked out at the crash site. Fuel exhaustion was one of the first things that was publically ruled out by the investigators - it's easy to rule out - look for leaked fuel, and check for fuel in tanks that haven't been breached.
This doesn't rule out fuel starvation - where for some reason, while there is plenty of fuel on board, it's not being delivered to the engines.
Also, redunant systems have a nasty habit of occasionally not being quite as redundant as the designer hoped. A recent example is the Boeing 747-400 (i.e. a late model 747, with all electronic instrumentation) which lost complete generator power, despite having 4 generators and independent power buses and an APU. The power was routed underneath the first class toilet - which blocked and overflowed. But it seems the 747 designers had thought of that eventuality, and had designed it with a tray under the toilets to ensure an overflow wouldn't go on something it shouldn't.
The tray was cracked. The water leaked right onto the equipment below, and the crew were left with nothing but battery power. Fortunately, they were not far from landing so battery power was sufficient, otherwise they may have had to go back to old fashioned celestial navigation.
There have been several incidents of modern airliners catching fire all by themselves. Fortunately, with the exception of TWA800 they have all been on the ground. But the conditions have been the same: stochiometric mixture of fuel vapour and air in a fuel tank, set off by an electrical fault.
I doubt the aircraft stalled: a large aircraft like a Boeing 777 will _not_ recover from a stall in 600 ft, and everyone would have been dead. If it stalled at all, it would have been just before touchdown while the crew were trying to arrest whatever sink rate they could before impact.
As for fuel exhaustion - that was ruled out very quickly - plenty of fuel leaked from at least one breached fuel tank. It's the first thing the investigators would have done - look in the tanks and see if there was fuel. That doesn't rule out fuel STARVATION though - you can have plenty of fuel on board, but something stopping it from reaching the engines.
Since this is the natural place for living room electronics: neatly installed in some under-TV cabinet, surely it behooves the manufacturer to design their equipment to live where many people are going to instinctively put them?