as opposed to open office, linux, and html5? he heheh hehehehehelmao
The only truly secure software is sitting inert on a cdrom in it's case. The rest of it is vulnerable (either through vulnerabilities discovered or not yet found and the exploits that use them)
If man made it, man can break it. If you don't believe this, you have already lost at the game that has become security. There is _always_ a way and always will be.
You can't rely on secure software to make yourself secure. There's no such thing. Defense in depth and behavior modification are the only things that work and neither has much to do with what software you use..
Ever notice that climate science is the only science where all empirical evidence points to the prevailing theory no matter what happens? If it rains too much, AGW. If theres a drought, it's AGW. If it snows a lot, AGW. If it doesn't snow at all? You guessed it, AGW. If it's an unusually cold winter, it's AGW. If it's an unusually warm winter, AGW. If it's too hot in the summer, AGW. If it's too cool in the summer? Must be AGW.
I'm not a denier or a scientist, I'm agnostic. I don't think we have enough data to determine the cause of global warming with any certainty, though I believe that climate change is real.
Just repeating an observation I've read about in an editorial by a physicist.
It's the only science where theory is presented as though it's proven fact before the research is conclusive, and no one challenges it, there's no oversight, and any attempt to bring up valid challenges to the methods used by AGW zealot scientists meets with red tape, refusal and the formation of what amounts to a straw committee made up of AGW zealots to oversee themselves. If it weren't pseudo science they'd welcome oversight by impartial third parties. They don't.
They hide stuff and adopt obstructionist policy opposed to handing over the data they base their conclusions on.
Climategate not withstanding, there are big problems with the climate science community.
Are you kidding? You can't even have a conversation with a pro-agw type about it. The minute you question anything about it, you become a conservative right wing teabagging conspiracy nut and can't get a word in edge wise unless you shout over them while they're spouting off about greenhouse gases and making up statistics on the spot. God forbid that you should think for yourself and hear all sides of an issue before drawing a conclusion. Never mind the facts and evidence that point to the fact that global warming is more than just CO2 levels.
It's like trying to talk a born-again christian fundamentalist into becoming a muslim. That conversation won't get very far.
My brother is one of those people. He's pretty uncomfortable to be around sometimes and constantly spouts off far left wing propaganda.
Often I can't wait for him to get into his V8 powered crown vic and go the hell home so I can have a normal conversation with the rest of my relatives. Did I mention he's a hypocrite? Half the time I pull up to his house (to drop off something from my parents or something) and all of his lights are on even though no one's there.
The last earthquake of this magnitude on the east coast was 1897 (also in mineral VA). our building codes here aren't set up with earthquakes in mind.
You can sneeze on some of these buildings and they'll collapse. A lot of them (at least in Maryland, in the older cities such as Annapolis and Baltimore) were built as early as the 1700s and the mortar is severely degraded. I'm expecting my house to be out of level when I get home as it's built in sandy soil that's probably subject to liquefaction and I'm pretty sure the foundation isn't more than 8' deep. I'd be surprised if it was 4'.
I'd honestly be surprised if my rental property (Baltimore brick house built in 1830) is still standing.
Laugh it up, but anything over mag 5 is pretty serious business here... We're having water main breaks, gas leaks and all sorts of problems.
One way to reconcile faith with science is to postulate that god (really a huge scientist operating a particle accelerator) created the earth and heavens with the big bang and he's watching his great science project unfold on it's own. Ancient writers of the bible had nothing to go on so had to make it all up.
He and his lab assistants (the angels) can communicate with us telepathically and know we're here.
The concept of time to us is greatly slowed down. Trillions of years to us is a picosecond to god. His experiment is still splattering on to the paper and will be for a very long time.
Then he'll do it again.
The end of days will be his experiment getting scraped off the paper (imperfect process) and we'll either be left on the paper and thrown into the trash to be incinerated (hell) or put into a viral culture (heaven) or where we'll live a few weeks (in God time) and be studied; to us it will seem like an eternity.
Not quite as romantic as the bible but maybe more accurate.
The old "our universe is a speck of dirt under a giant's fingernail" theory with a twist.
Our little universe with it's expanding galaxies is nothing more than a very complex atom being split in a much bigger space time continuum than we can possibly imagine.
My version is just as provable as the bible's and jives with science, so there!
15-18 year olds don't know the law. When I was that age, if I was hit by someone I hit them back twice as hard, or got my ass kicked. If you didn't you'd find yourself getting your ass kicked all the time. The people that fought back sent a message and the bullies moved on to weaker targets that cower and take the beating, aka "pussies".
The key is not to do it on school property. I was smart enough to know that, though going to jail never entered my mind.
I was on the small side so I was a frequent target until I got tired of it and started fucking people up. The last time it happened was 10th grade. Some asshole smacked me in the face when he walked by, on the bus. I got up, kicked him in the chest (by grabbing an overhead bar on the bus and swinging/kicking the guy in the chest), while he was on the ground gasping for air I kicked him in his face with my doc martens til I was tired and my friends pulled me off. When I was done he had black eye and bloody nose. Then I threw his books off the moving bus. My anger for this kid had been building, over months, due to his bullying. I simply snapped and wrecked his face.
Of course that was before video cameras, and was also on a MTA bus (not a yellow bus)
No one in my neighborhood or school ever fucked with me, or my friends, again. When you are getting bullied, it shouldn't be against the law to defend yourself and establish your place in the pecking order. It's a rite of passage.
Other times I got my ass kicked. However even if you get your ass kicked, the bullies generally back off. If you are brave enough to fight back you might be brave enough to have a knife or pipe in your back pack next time.
Actually Linus has no issues with C++, as long as it's not used in the kernel. C++ is too slow for kernel development because of all the object marshaling.
He says for userland coding it's fine. The negative side of OOP is magnified in a kernel making it too slow.
User programs spend almost all of their time waiting for input.
Your co-worker needs to read the entire article/email instead of stopping at what he wants to hear. Maybe he wouldn't be so irrational.
The problem is the configuration files for the beans. They are proprietary. You can't deploy a jar written for jboss (or websphere, or BEA) anywhere but the type of app server it was written on. You can cut and paste the code into the gui for another app server, yes. However it's not write once run anywhere. It's write once, run on this app server only. The app server can run on any platform. In that respect it is write once run anywhere, as long as the app server runs on the "anywhere".
There hasn't been a GC invented that does what it's supposed to. I had a MS engineer (that helped write IIS) tell me at a MS conference on campus in Redmond : "Don't ever rely on garbage collection; _explicitly_ clean up your objects. The GC is nothing but a marketing tool to sell product. It doesn't really work."
You ever work somewhere where the NT/2000 servers needed to be rebooted daily? The code was written by sloppy programmers. It wasn't the operating system.
given that most (if not all) smartphones have video cameras in them, and a huge number of people have smartphones, it should be patently obvious that it's highly likely that someone is filming you if you are doing anything out of the ordinary, especially if you are beating someone to within an inch of their life out on a public street.
I'd like to know why the author ignores brilliant people that are active right now, like Benjamin Carson, Linus Torvalds, Stephen Hawking, and the people that win Nobel prizes every year (at least in medicine, literature and the sciences, the peace prize is a bullshit popularity contest)
Sorry I left some people out but hopefully I've made my point. The author of that article is disconnected. He's simply wrong.
you've never had an issue, but other people have from the issues you caused. you didn't notice because you were being selfish and were in your own little world. I hope you get a very expensive ticket before you kill someone.
They should be called intentionals. Whatever you did to cause the car wreck you did intentionally. You willingly engaged in behavior that was incompatible with driving leading to a car wreck. Actual "car accidents" are extremely rare.
Someone either wasn't paying attention because they were on the phone or playing with their radio, driving too fast for conditions, drunk, speeding, didn't maintain their car adequately or they were targeted by the mob.
About the only type of wrecks that are actually an accident is a wreck caused by loss of control due to tire failure from debris in the road, sudden onset of symptoms from a new (to you) medical condition, loss of control due to flying debris hitting your car, or a manufacturing defect leading to catastrophic unpredictable failure of critical systems, maybe a meteor falling from the sky.
If it was preventable on your part, it's not an accident, you caused it on purpose.
the bigger problem outside of steering with your knees is divided attention. You need to have your full attention on the road or bad shit happens and you piss everyone off.
When you are on a cell phone while driving you do dumb shit, I don't care who you are. I've seen people slow down to 45mph in the passing lane, change lanes right into another car (true story), and just stop the car in traffic at rush hour wildly gesticulating and yelling at whoever is on the other end of the call. The worst are the people that do 5mph on a one lane street and retard traffic because they are being a celltard. I saw a woman on a cell phone in the fast lane yank her wheel and recklessly change lanes across 4 lanes of 65mph traffic without even looking because she was about to miss her exit. She caused a tractor trailer to jack-knife.
Pull the fuck over and make your stupid call. Get out of my way; get off the fucking road. I'll take the guy driving with no hands any day, doing the speed limit or faster, over a moron on a phone slowing me down or changing lanes into my car. That drives me batshit crazy when I'm trying to get to work. If someone road rages, pulls out a piece and kills such an asshole I didn't see anything. That's a justifiable homicide in my opinion, a perfect example of natural selection at work. I'd cheer.
"I was a bit disappointed in the book as I didn't learn as much as I would have liked, this is really more of a "how to do the basics" and doesn't provide much depth on Audacity or audio concepts in general."
You can't really expect a book that teaches a piece of software to cover audio concepts and teach you how to mix. There are whole books devoted entirely to recording engineering, mix engineering, and mastering (each of which is a discipline that takes years of practice to master, usually people specialize in one of them), which are some of the activities one would do on Audacity.
There are entire volumes dedicated to mic placement alone.
Don't expect a book like this to school you on engineering. It won't. Read the book, learn the software, then you can begin learning something about engineering.
Mastery of any type of audio engineering is a very long road to travel indeed...
There is very little distortion with tubes unless you overdrive them. They do clip more musically than silicon, yes, but that's not the only reason people use them.
A tube mic preamp can be much cleaner and musical with less THD than any amplifier on a chip.
Some of the cleanest, most distortion free preamps in the world are tube driven. I'm not talking about $200 t00b amps from guitar center, but amps like the universal audio 610 or 6176 or some of the Manley stuff. If you are getting a distorted signal from these you are doing it wrong, unless you are using the distortion as an effect.
There is equally great FET technology though (think Neve and Great River) which also clip musically and use transistors.
Most analog audio technology has soft clip properties... however this is probably in the middle of the list of reasons why analog audio gear rocks. Cheap analog gear sucks unless used as a "cheap analog gear" effect. It's noisy, typically the circuit boards are filthy and your work sounds like shit due to the accumulation of noise across all of your tracks. It adds up fast;-)
/don fireproof underwear I thought it was due to a lack of ability to run applications (out of the box) used by, well, everyone?
Don't give me the WINE argument either... I can do WINE, so can a lot of other geeks but put an average Mac or Windows user on a linux system and they'll be wondering where outlook, word and excel are. None of them will have any idea how to install WINE, or even that WINE exists. They only know that their professor only accepts Word documents or that the accountant at work only accepts their expense report in the form of an Excel spreadsheet running their custom macros.
"crap! I can't write my paper or do my expense report. f**k! My office install cd isn't working! Where's outlook?" That's what's going through most user's minds the first time they use linux.
When you can put an office (or [insert windows software here]) install cd in the cd drive on a box running a linux distro, and the install Just Works(tm), linux will gain traction.
Linux distros needs to be easy enough that people don't need an IT professional in the house to use it, install their software, get connected and do day to day tasks using the software which is often required by the people they have to work with. A lot of users have no choice.
The FOSS community isn't interested in gaining traction on the desktop. Not interested _at all_.
If they are they are going about it completely wrong. Desktop penetration is only achieved by making your OS easy to use and keeping the pain manageable.
The only distro that comes close to reaching this goal is Ubuntu and they're not doing that great of a job. That's why apple is spanking linux in the desktop market.
A successful distro will need to hire a focus group of typical DFUs, find out what they need to fix, then fix it. Users don't give a rat's ass about fragmentation and users are what you need for desktop penetration.
The major area of linux penetration in the enterprise is server OS. There are few "enterprise" networks running linux on the desktop. Apple has distanced itself from the enterprise server market. So it could be said that the linux and Apple markets are complementary and they don't really compete. As well, at least in my world, users aren't permitted on the servers and admins typically use key authentication (either managed or not) which isn't vulnerable to AD exploits.
Of course, like any machine, you can easily root the box with physical access, I don't care if it's windows, linux or mac. From there all sorts of nasty stuff becomes possible, like root access. All you need is a set of install disks and a recovery console.
Then there's another issue of people depending on packages from the distro maintainer for critical services. You can't patch until the distro releases the packages in this case, or you uninstall the packages and build it from source. When the last SSL worm happened (September, 2002 OpenSSL 0.9.6d), distros and vendors were ugly slow to released patched packages. It took months, and during that time, everyone was vulnerable. From then on any sane admin started compiling their LAMP setups from source so they can patch as soon as possible. The OpenSSL folks released a patch the _next day_ after the advisory(kudos!). Calls to our "Secure" apache vendor were met with "we're working on it" for weeks on end. We weren't authorized to use any other vendor or distro (it was at a bank).
I was issued an ultimatum by our CISO, patch it by 5PM tomorrow or we are shutting down your server farm. I had no choice but to build from source. Luckily I had extensive experience building from source (I am a developer) so was able to cope and get the job done (30 servers, that was a very long day). At the time our administrator had been fired and I was filling in for him.
So while you are right, OSS projects patch fast, distros don't release patched binaries with any speed resembling fast, and actually _getting_ the patch can take weeks unless you compile the service from source or use a distro like Gentoo (most enterprise use package distros like SuSE, Ubuntu, Debian, Red Hat etc). All is not as rosy as people claim it is... unless your game is upped to the point where you are self sufficient and not dependent on packages. If you call yourself an administrator it goes without saying that you need to be here. If you run exposed services on binaries from distro packages you are playing professional russian roulette. You should at least familiarize yourself with compiling from source in case you need to compile a service in an emergency.
It could save your servers and live data and help you avoid having a really bad week. It can mean the difference between pulling the plug or continued operation.
Slashdot Mirror
as opposed to open office, linux, and html5?
he heheh hehehehehelmao
The only truly secure software is sitting inert on a cdrom in it's case. The rest of it is vulnerable (either through vulnerabilities discovered or not yet found and the exploits that use them)
If man made it, man can break it. If you don't believe this, you have already lost at the game that has become security. There is _always_ a way and always will be.
You can't rely on secure software to make yourself secure. There's no such thing. Defense in depth and behavior modification are the only things that work and neither has much to do with what software you use..
Ever notice that climate science is the only science where all empirical evidence points to the prevailing theory no matter what happens? If it rains too much, AGW. If theres a drought, it's AGW. If it snows a lot, AGW. If it doesn't snow at all? You guessed it, AGW. If it's an unusually cold winter, it's AGW. If it's an unusually warm winter, AGW. If it's too hot in the summer, AGW. If it's too cool in the summer? Must be AGW.
I'm not a denier or a scientist, I'm agnostic. I don't think we have enough data to determine the cause of global warming with any certainty, though I believe that climate change is real.
Just repeating an observation I've read about in an editorial by a physicist.
It's the only science where theory is presented as though it's proven fact before the research is conclusive, and no one challenges it, there's no oversight, and any attempt to bring up valid challenges to the methods used by AGW zealot scientists meets with red tape, refusal and the formation of what amounts to a straw committee made up of AGW zealots to oversee themselves. If it weren't pseudo science they'd welcome oversight by impartial third parties. They don't.
They hide stuff and adopt obstructionist policy opposed to handing over the data they base their conclusions on.
Climategate not withstanding, there are big problems with the climate science community.
Are you kidding? You can't even have a conversation with a pro-agw type about it. The minute you question anything about it, you become a conservative right wing teabagging conspiracy nut and can't get a word in edge wise unless you shout over them while they're spouting off about greenhouse gases and making up statistics on the spot. God forbid that you should think for yourself and hear all sides of an issue before drawing a conclusion. Never mind the facts and evidence that point to the fact that global warming is more than just CO2 levels.
It's like trying to talk a born-again christian fundamentalist into becoming a muslim. That conversation won't get very far.
My brother is one of those people. He's pretty uncomfortable to be around sometimes and constantly spouts off far left wing propaganda.
Often I can't wait for him to get into his V8 powered crown vic and go the hell home so I can have a normal conversation with the rest of my relatives. Did I mention he's a hypocrite? Half the time I pull up to his house (to drop off something from my parents or something) and all of his lights are on even though no one's there.
you have to be an idiot to deny the earth is getting warmer. that is settled. what isn't settled is the cause.
The last earthquake of this magnitude on the east coast was 1897 (also in mineral VA). our building codes here aren't set up with earthquakes in mind.
You can sneeze on some of these buildings and they'll collapse. A lot of them (at least in Maryland, in the older cities such as Annapolis and Baltimore) were built as early as the 1700s and the mortar is severely degraded. I'm expecting my house to be out of level when I get home as it's built in sandy soil that's probably subject to liquefaction and I'm pretty sure the foundation isn't more than 8' deep. I'd be surprised if it was 4'.
I'd honestly be surprised if my rental property (Baltimore brick house built in 1830) is still standing.
Laugh it up, but anything over mag 5 is pretty serious business here... We're having water main breaks, gas leaks and all sorts of problems.
Hopefully the building codes get revised.
One way to reconcile faith with science is to postulate that god (really a huge scientist operating a particle accelerator) created the earth and heavens with the big bang and he's watching his great science project unfold on it's own. Ancient writers of the bible had nothing to go on so had to make it all up.
He and his lab assistants (the angels) can communicate with us telepathically and know we're here.
The concept of time to us is greatly slowed down. Trillions of years to us is a picosecond to god. His experiment is still splattering on to the paper and will be for a very long time.
Then he'll do it again.
The end of days will be his experiment getting scraped off the paper (imperfect process) and we'll either be left on the paper and thrown into the trash to be incinerated (hell) or put into a viral culture (heaven) or where we'll live a few weeks (in God time) and be studied; to us it will seem like an eternity.
Not quite as romantic as the bible but maybe more accurate.
The old "our universe is a speck of dirt under a giant's fingernail" theory with a twist.
Our little universe with it's expanding galaxies is nothing more than a very complex atom being split in a much bigger space time continuum than we can possibly imagine.
My version is just as provable as the bible's and jives with science, so there!
15-18 year olds don't know the law. When I was that age, if I was hit by someone I hit them back twice as hard, or got my ass kicked. If you didn't you'd find yourself getting your ass kicked all the time. The people that fought back sent a message and the bullies moved on to weaker targets that cower and take the beating, aka "pussies".
The key is not to do it on school property. I was smart enough to know that, though going to jail never entered my mind.
I was on the small side so I was a frequent target until I got tired of it and started fucking people up. The last time it happened was 10th grade. Some asshole smacked me in the face when he walked by, on the bus. I got up, kicked him in the chest (by grabbing an overhead bar on the bus and swinging/kicking the guy in the chest), while he was on the ground gasping for air I kicked him in his face with my doc martens til I was tired and my friends pulled me off. When I was done he had black eye and bloody nose. Then I threw his books off the moving bus. My anger for this kid had been building, over months, due to his bullying. I simply snapped and wrecked his face.
Of course that was before video cameras, and was also on a MTA bus (not a yellow bus)
No one in my neighborhood or school ever fucked with me, or my friends, again. When you are getting bullied, it shouldn't be against the law to defend yourself and establish your place in the pecking order. It's a rite of passage.
Other times I got my ass kicked. However even if you get your ass kicked, the bullies generally back off. If you are brave enough to fight back you might be brave enough to have a knife or pipe in your back pack next time.
Actually Linus has no issues with C++, as long as it's not used in the kernel. C++ is too slow for kernel development because of all the object marshaling.
He says for userland coding it's fine. The negative side of OOP is magnified in a kernel making it too slow.
User programs spend almost all of their time waiting for input.
Your co-worker needs to read the entire article/email instead of stopping at what he wants to hear. Maybe he wouldn't be so irrational.
The problem is the configuration files for the beans. They are proprietary. You can't deploy a jar written for jboss (or websphere, or BEA) anywhere but the type of app server it was written on. You can cut and paste the code into the gui for another app server, yes. However it's not write once run anywhere. It's write once, run on this app server only. The app server can run on any platform. In that respect it is write once run anywhere, as long as the app server runs on the "anywhere".
I learned this in 1997.
There hasn't been a GC invented that does what it's supposed to. I had a MS engineer (that helped write IIS) tell me at a MS conference on campus in Redmond : "Don't ever rely on garbage collection; _explicitly_ clean up your objects. The GC is nothing but a marketing tool to sell product. It doesn't really work."
You ever work somewhere where the NT/2000 servers needed to be rebooted daily? The code was written by sloppy programmers. It wasn't the operating system.
given that most (if not all) smartphones have video cameras in them, and a huge number of people have smartphones, it should be patently obvious that it's highly likely that someone is filming you if you are doing anything out of the ordinary, especially if you are beating someone to within an inch of their life out on a public street.
I'd like to know why the author ignores brilliant people that are active right now, like Benjamin Carson, Linus Torvalds, Stephen Hawking, and the people that win Nobel prizes every year (at least in medicine, literature and the sciences, the peace prize is a bullshit popularity contest)
Sorry I left some people out but hopefully I've made my point. The author of that article is disconnected. He's simply wrong.
you've never had an issue, but other people have from the issues you caused. you didn't notice because you were being selfish and were in your own little world. I hope you get a very expensive ticket before you kill someone.
They should be called intentionals. Whatever you did to cause the car wreck you did intentionally. You willingly engaged in behavior that was incompatible with driving leading to a car wreck. Actual "car accidents" are extremely rare.
Someone either wasn't paying attention because they were on the phone or playing with their radio, driving too fast for conditions, drunk, speeding, didn't maintain their car adequately or they were targeted by the mob.
About the only type of wrecks that are actually an accident is a wreck caused by loss of control due to tire failure from debris in the road, sudden onset of symptoms from a new (to you) medical condition, loss of control due to flying debris hitting your car, or a manufacturing defect leading to catastrophic unpredictable failure of critical systems, maybe a meteor falling from the sky.
If it was preventable on your part, it's not an accident, you caused it on purpose.
the bigger problem outside of steering with your knees is divided attention. You need to have your full attention on the road or bad shit happens and you piss everyone off.
When you are on a cell phone while driving you do dumb shit, I don't care who you are. I've seen people slow down to 45mph in the passing lane, change lanes right into another car (true story), and just stop the car in traffic at rush hour wildly gesticulating and yelling at whoever is on the other end of the call. The worst are the people that do 5mph on a one lane street and retard traffic because they are being a celltard. I saw a woman on a cell phone in the fast lane yank her wheel and recklessly change lanes across 4 lanes of 65mph traffic without even looking because she was about to miss her exit. She caused a tractor trailer to jack-knife.
Pull the fuck over and make your stupid call. Get out of my way; get off the fucking road. I'll take the guy driving with no hands any day, doing the speed limit or faster, over a moron on a phone slowing me down or changing lanes into my car. That drives me batshit crazy when I'm trying to get to work. If someone road rages, pulls out a piece and kills such an asshole I didn't see anything. That's a justifiable homicide in my opinion, a perfect example of natural selection at work. I'd cheer.
"I was a bit disappointed in the book as I didn't learn as much as I would have liked, this is really more of a "how to do the basics" and doesn't provide much depth on Audacity or audio concepts in general."
You can't really expect a book that teaches a piece of software to cover audio concepts and teach you how to mix. There are whole books devoted entirely to recording engineering, mix engineering, and mastering (each of which is a discipline that takes years of practice to master, usually people specialize in one of them), which are some of the activities one would do on Audacity.
There are entire volumes dedicated to mic placement alone.
Don't expect a book like this to school you on engineering. It won't. Read the book, learn the software, then you can begin learning something about engineering.
Mastery of any type of audio engineering is a very long road to travel indeed...
don't hate the player, hate the game.
There is very little distortion with tubes unless you overdrive them. They do clip more musically than silicon, yes, but that's not the only reason people use them.
;-)
A tube mic preamp can be much cleaner and musical with less THD than any amplifier on a chip.
Some of the cleanest, most distortion free preamps in the world are tube driven. I'm not talking about $200 t00b amps from guitar center, but amps like the universal audio 610 or 6176 or some of the Manley stuff. If you are getting a distorted signal from these you are doing it wrong, unless you are using the distortion as an effect.
There is equally great FET technology though (think Neve and Great River) which also clip musically and use transistors.
Most analog audio technology has soft clip properties... however this is probably in the middle of the list of reasons why analog audio gear rocks. Cheap analog gear sucks unless used as a "cheap analog gear" effect. It's noisy, typically the circuit boards are filthy and your work sounds like shit due to the accumulation of noise across all of your tracks. It adds up fast
1982 called. They want their joke back.
"intent" is a very important legal concept. hopefully the judge agrees.
/don fireproof underwear
I thought it was due to a lack of ability to run applications (out of the box) used by, well, everyone?
Don't give me the WINE argument either... I can do WINE, so can a lot of other geeks but put an average Mac or Windows user on a linux system and they'll be wondering where outlook, word and excel are. None of them will have any idea how to install WINE, or even that WINE exists. They only know that their professor only accepts Word documents or that the accountant at work only accepts their expense report in the form of an Excel spreadsheet running their custom macros.
"crap! I can't write my paper or do my expense report. f**k! My office install cd isn't working! Where's outlook?" That's what's going through most user's minds the first time they use linux.
When you can put an office (or [insert windows software here]) install cd in the cd drive on a box running a linux distro, and the install Just Works(tm), linux will gain traction.
Linux distros needs to be easy enough that people don't need an IT professional in the house to use it, install their software, get connected and do day to day tasks using the software which is often required by the people they have to work with. A lot of users have no choice.
The FOSS community isn't interested in gaining traction on the desktop. Not interested _at all_.
If they are they are going about it completely wrong. Desktop penetration is only achieved by making your OS easy to use and keeping the pain manageable.
The only distro that comes close to reaching this goal is Ubuntu and they're not doing that great of a job. That's why apple is spanking linux in the desktop market.
A successful distro will need to hire a focus group of typical DFUs, find out what they need to fix, then fix it. Users don't give a rat's ass about fragmentation and users are what you need for desktop penetration.
The major area of linux penetration in the enterprise is server OS. There are few "enterprise" networks running linux on the desktop. Apple has distanced itself from the enterprise server market. So it could be said that the linux and Apple markets are complementary and they don't really compete. As well, at least in my world, users aren't permitted on the servers and admins typically use key authentication (either managed or not) which isn't vulnerable to AD exploits.
Of course, like any machine, you can easily root the box with physical access, I don't care if it's windows, linux or mac. From there all sorts of nasty stuff becomes possible, like root access. All you need is a set of install disks and a recovery console.
Then there's another issue of people depending on packages from the distro maintainer for critical services. You can't patch until the distro releases the packages in this case, or you uninstall the packages and build it from source. When the last SSL worm happened (September, 2002 OpenSSL 0.9.6d), distros and vendors were ugly slow to released patched packages. It took months, and during that time, everyone was vulnerable. From then on any sane admin started compiling their LAMP setups from source so they can patch as soon as possible. The OpenSSL folks released a patch the _next day_ after the advisory(kudos!). Calls to our "Secure" apache vendor were met with "we're working on it" for weeks on end. We weren't authorized to use any other vendor or distro (it was at a bank).
I was issued an ultimatum by our CISO, patch it by 5PM tomorrow or we are shutting down your server farm. I had no choice but to build from source. Luckily I had extensive experience building from source (I am a developer) so was able to cope and get the job done (30 servers, that was a very long day). At the time our administrator had been fired and I was filling in for him.
So while you are right, OSS projects patch fast, distros don't release patched binaries with any speed resembling fast, and actually _getting_ the patch can take weeks unless you compile the service from source or use a distro like Gentoo (most enterprise use package distros like SuSE, Ubuntu, Debian, Red Hat etc). All is not as rosy as people claim it is... unless your game is upped to the point where you are self sufficient and not dependent on packages. If you call yourself an administrator it goes without saying that you need to be here. If you run exposed services on binaries from distro packages you are playing professional russian roulette. You should at least familiarize yourself with compiling from source in case you need to compile a service in an emergency.
It could save your servers and live data and help you avoid having a really bad week. It can mean the difference between pulling the plug or continued operation.
Exactly. The bigger picture is concerning because Apple really *is* poised to become the Next Big Thing on the Desktop
--
not at those prices...
Having said that, this exploit still requires an admin password to escalate privileges
--
Or a privilege escalation exploit...
the "exploits" for Macs these guys found require an amazing amount of stupidity
---
Out in the real world, there's an amazing amount of stupidity.