Indeed. Personally I'll upgrade everything except the kernel remotely and even the kernels are hand picked by me.
Some hosting companies can take several hours to process a reboot request. and then they have to call in a special tech ($200/hr) to chose another boot option if the system can't come up at all with the upgraded kernel. Even for hosting that's in the same city as me will take me an hour to get there just to handle a reboot.
I had a few six hour outages before I became very conservative,
VIA chipsets were for the most part solid but slow. The major exception being around the Aathlon XP or worse yet the MP where things were pretty much unusable.
At least with NForce chipsets you can have descent HD transfer and networking performance. My Nforce chipsets have been pretty much solid at least in Linux.
SiS on the other hand tended to be slow and unstable on any OS. That's why if I had a choice of what manufacturer would have quit the chipset buisness first it would have been SiS.
This is all about making sure all Open source apps work on windows so that the likelihood of there being a killer app that won't work on windows is reduced.
The downside for Microsoft is that now OSS apps can compete directly with windows apps and eventually if they take over then managers may very well wonder why they are paying for windows if everything they use runs on Linux anyways. But that is a much slower rate of loss than you would get from a much needed app that runs only on Linux.
They really don't. Quite often sites like Expedia will mark up the price by several hundred dollars.
I ended up discovering the aggregators are useless anyways. When I booked my last flight it turned out the cheapest airline (NWA) wasn't even listed on Expedia or any of the other "aggregators".
I suspect Ryanair is mostly upset about the screen with markup. If all the sites did was search for the cheapest airfare and forward you then there would be nothing whatsoever Ryanair could do about it.
I think it's more simple than that. I bet you the system is just not designed for bulk wage changes meaning someone would have to go through each contractor/ pay grade and reduce it to minimum wage and then to back again when everything is restored.
The marriage was broken up because the guy wanted to cheat on his wife but got caught instead. The prank actually did a wife a favor.
I have no sympathy whatsoever for this guy. If you want to sleep around then suck it up and get a divorce. Promising to be faithful and then sneaking off behind her back is beyond contempt.
From the article:The researchers claimed that the plasmonic collimator effect is similar to the way phased-array antennas steer a beam, creating the possibility of steering laser beams with no moving parts.
Wow you have managed to go on a complete rant while ignoring everything I said.
What do you think your CIO will say if you get rooted and your answer is "well there was a bugfix but it wasn't a known vulnerability when the patch came out so I didn't install it"?
Bugfixes are bugfixes and even in the case of security bugs you should be testing before deployment. Don't know if you need to install it? Well just read the freaking changelog and see if it affects a driver or subsystem your using. Even the Payment Card Industry standards require you to test security updates before deployment.
Even if it's not a security bug you may very well want to install the patch to avoid a possible crash when your not expecting it. Better a controlled outage than a crash at 4 am.
In both. There were some that were Linux only but quite a few affected OpenBSD as well.
It's not that they didn't do a good job and they clearly did a much better job than the SSH daemon they replaced it's just that the Linux distros adopting it increased it's userbase by a lot and as a side affect increased the the number of people who saw a need to look at the code.
It's funny how well that doesn't work for them. I still remember the number of bugs that were suddenly discovered in openSSH right after the Linux distros switched over to it.
Under what conditions would a patch not be worth applying? Thanks to the new shorter dev cycle once a kernel is marked stable it doesn't need or get new features.. only bugfixes.
There is no reason whatsoever to run a non bugfixed kernel. 2.2.x, 2.4.x and every 2.6.x branch since Linus switched over to the new shorter dev cycle are still actively maintained with bugfixes.
If you want stability just stay on the current branch your on.. ex 2.6.23.x. No new features will be added only bugfixes. Need to know if you need to apply the patch? Just check the change log to see if the bug is in any subsystem you use.
Otherwise you risk someone discovering a bug is exploitable after the patch was added to the kernel.
Congratulations your exactly the reason Linus doesn't want a big flashing "Security" sign.
Linus' point was that most bugs can be potential security problems and if you ignore anything but security fixes you risk not patching in the case of a bug being discovered exploitable after the fix goes into the kernel.
Talk about rose tinted glasses.. The 2.4/2.5 split that I remember left me at times with TWO unstable kernel series thanks to 2.5.x not being ready for production yet and maintainers trying to backport drivers and to 2.4.x so it could still handle the latest hardware.
At the worst of it I recall setting up a state of the art server with a SCSI card that crashed randomly on 2.4.x and wouldn't boot on 2.5.x series kernels. Lucky for me the bug was fixed in 2.5.x a week later.
The new way is easy.. new features and drivers get added to the latest 2.6.x-rc only and only bug fixes get added to the old kernels. This means that if I want to be sure I'm rock solid I just install the latest patch to the kernel I'm running and I can be sure no one has tried to add new features or drivers that would otherwise destabilize my stuff.
Why anyone would possibly want to go back to the old way is beyond me.
There are multiple bugfix only branches. 2.6.16.x to 2.6.25.x are all still actively maintained.
The simple fact is that the new model has actually caused Linux distros to have more stable kernels now that vendors aren't trying to constantly backport things from the unstable branch.
Shorter dev cycles were one of the best ideas Linus ever had.
Slashdot Mirror
It seems no one has bothered to actually read the story.
The game was seized along with knives, chisels and bolt cutters from a group of climate protesters.
I'd say the seizure of those items was completely justified.
Indeed. Personally I'll upgrade everything except the kernel remotely and even the kernels are hand picked by me.
Some hosting companies can take several hours to process a reboot request. and then they have to call in a special tech ($200/hr) to chose another boot option if the system can't come up at all with the upgraded kernel. Even for hosting that's in the same city as me will take me an hour to get there just to handle a reboot.
I had a few six hour outages before I became very conservative,
VIA chipsets were for the most part solid but slow. The major exception being around the Aathlon XP or worse yet the MP where things were pretty much unusable.
At least with NForce chipsets you can have descent HD transfer and networking performance. My Nforce chipsets have been pretty much solid at least in Linux.
SiS on the other hand tended to be slow and unstable on any OS. That's why if I had a choice of what manufacturer would have quit the chipset buisness first it would have been SiS.
Losing the slower / lower quality players can only be a good thing. Now if only SIS would do the same.
The only chip set I hated more than VIA was SIS.
SIS could out glitch VIA every time.
This is all about making sure all Open source apps work on windows so that the likelihood of there being a killer app that won't work on windows is reduced.
The downside for Microsoft is that now OSS apps can compete directly with windows apps and eventually if they take over then managers may very well wonder why they are paying for windows if everything they use runs on Linux anyways. But that is a much slower rate of loss than you would get from a much needed app that runs only on Linux.
The most nonsensical part is that round trip costs less than single direction.
They really don't. Quite often sites like Expedia will mark up the price by several hundred dollars.
I ended up discovering the aggregators are useless anyways. When I booked my last flight it turned out the cheapest airline (NWA) wasn't even listed on Expedia or any of the other "aggregators".
I suspect Ryanair is mostly upset about the screen with markup. If all the sites did was search for the cheapest airfare and forward you then there would be nothing whatsoever Ryanair could do about it.
I think it's more simple than that. I bet you the system is just not designed for bulk wage changes meaning someone would have to go through each contractor/ pay grade and reduce it to minimum wage and then to back again when everything is restored.
Odds are that's thousands of changes.
The marriage was broken up because the guy wanted to cheat on his wife but got caught instead. The prank actually did a wife a favor.
I have no sympathy whatsoever for this guy. If you want to sleep around then suck it up and get a divorce. Promising to be faithful and then sneaking off behind her back is beyond contempt.
From the article:The researchers claimed that the plasmonic collimator effect is similar to the way phased-array antennas steer a beam, creating the possibility of steering laser beams with no moving parts.
Wow you have managed to go on a complete rant while ignoring everything I said.
What do you think your CIO will say if you get rooted and your answer is "well there was a bugfix but it wasn't a known vulnerability when the patch came out so I didn't install it"?
Bugfixes are bugfixes and even in the case of security bugs you should be testing before deployment. Don't know if you need to install it? Well just read the freaking changelog and see if it affects a driver or subsystem your using. Even the Payment Card Industry standards require you to test security updates before deployment.
Even if it's not a security bug you may very well want to install the patch to avoid a possible crash when your not expecting it. Better a controlled outage than a crash at 4 am.
In both. There were some that were Linux only but quite a few affected OpenBSD as well.
It's not that they didn't do a good job and they clearly did a much better job than the SSH daemon they replaced it's just that the Linux distros adopting it increased it's userbase by a lot and as a side affect increased the the number of people who saw a need to look at the code.
It's funny how well that doesn't work for them. I still remember the number of bugs that were suddenly discovered in openSSH right after the Linux distros switched over to it.
Under what conditions would a patch not be worth applying? Thanks to the new shorter dev cycle once a kernel is marked stable it doesn't need or get new features.. only bugfixes.
There is no reason whatsoever to run a non bugfixed kernel. 2.2.x, 2.4.x and every 2.6.x branch since Linus switched over to the new shorter dev cycle are still actively maintained with bugfixes.
If you want stability just stay on the current branch your on.. ex 2.6.23.x. No new features will be added only bugfixes. Need to know if you need to apply the patch? Just check the change log to see if the bug is in any subsystem you use.
Otherwise you risk someone discovering a bug is exploitable after the patch was added to the kernel.
Congratulations your exactly the reason Linus doesn't want a big flashing "Security" sign.
Linus' point was that most bugs can be potential security problems and if you ignore anything but security fixes you risk not patching in the case of a bug being discovered exploitable after the fix goes into the kernel.
Talk about rose tinted glasses.. The 2.4 /2.5 split that I remember left me at times with TWO unstable kernel series thanks to 2.5.x not being ready for production yet and maintainers trying to backport drivers and to 2.4.x so it could still handle the latest hardware.
At the worst of it I recall setting up a state of the art server with a SCSI card that crashed randomly on 2.4.x and wouldn't boot on 2.5.x series kernels. Lucky for me the bug was fixed in 2.5.x a week later.
The new way is easy.. new features and drivers get added to the latest 2.6.x-rc only and only bug fixes get added to the old kernels. This means that if I want to be sure I'm rock solid I just install the latest patch to the kernel I'm running and I can be sure no one has tried to add new features or drivers that would otherwise destabilize my stuff.
Why anyone would possibly want to go back to the old way is beyond me.
There are multiple bugfix only branches. 2.6.16.x to 2.6.25.x are all still actively maintained.
The simple fact is that the new model has actually caused Linux distros to have more stable kernels now that vendors aren't trying to constantly backport things from the unstable branch.
Shorter dev cycles were one of the best ideas Linus ever had.
The problem with this is that when the device is on it's alerting the OS to any changes.
When it comes back online it still needs to rescan the USB check network connectivity (and get it's IP again) etc.
Vote for the bill that defines the fisa court as the only means for setting wiretaps and lose out on the immunity issue or lose out entirely?
Lesser of two evils here.
MSN works fine on Linux. I use Pidgin (formerly GAIM) to chat with work contacts and push them to google messanger when MSN goes down.
No MS Windows needed.
Unless you have an unlimited incoming plan that starts at $25+ with Telus (don't know for the other carriers) Your paying for incoming calls.
Land line calls incoming and outgoing are free as long as the outgoing call isn't long distance so that's how they justify it.
So if your not a laptop user and aren't currently benchmarking your drive how long will it last?
What is the power usage for real world office/ web browsing type use?