I have a mid 2010 macbook pro, it has the nvidia graphics and is running lion... It doesn't crash every 5 minutes, and has been up since the time i actually installed lion about 5 days ago.
Some 6 years ago i had a laptop with a 1024x768 internal screen which i carried round with me, and a 1280x1024 screen on my desk to which the laptop was connected whenever i was in the office... It ran linux, and worked perfectly.
Your problem actually sounds like the opposite of the traditional X11 configuration problem...
These days, the system tries to detect the capabilities of the monitor connected to it, whereas back in the days with linux you had to tell the system what capabilities your monitor had. The problem is when things go wrong with the auto detection and people have forgotten how to manually override things...
Over 10 years ago, i had similar problems to yours but with windows, linux gave me no problems at all because it simply did what it was told and didn't try to be too smart.
More recently intact, i have a TV set that can do 1080p but doesn't seem to advertise the fact properly... Some devices work with it, some don't... I can't get OSX or Windows to talk 1080p to it, and neither will Linux by default but if i manually modify the X11 config it will... I have no idea how to make the necessary changes under OSX/Windows.
Out of interest, what were you trying to get the systems "joined up and working" with? If it was an Active Directory environment then of course it would be more difficult to join anything non windows to it, that's how it's designed, so MS can claim "support" for joining non windows systems, but intentionally make it as difficult as possible to discourage you from using such systems.
Also the biggest problem with AD is security, get yourself an internal pen test and give them just a single ethernet socket to get started... If they're remotely competent they will have domain admin access before lunchtime.
Linux admins are not so much cheaper, as the general standard of windows admins is lower... For equivalent levels of competence the price is about the same (and such people are generally able to use the other system to some level too), "cheaper" only comes around because there are lots of people with virtually no knowledge whatsoever calling themselves windows admins.
If you let everybody speak, and let everybody listen, the truth will be known.
However, the mass media is controlled by a very small group... While everyone may be able to speak, only the mass media will be listened to by any significant proportion of people and thus their agendas are furthered and everything else ignored.
If someone were to put up their own website explaining their side, how would anyone even learn of the existence of that site?
There is no way to be heard without money and power, and the only way to get money and power is to be a part of the current system and thus have a vested interest in maintaining the status quo.
The vast majority believe what they hear on the media, and never bother to question it... If they heard an alternative viewpoint they might believe that too, but why would those who control the media ever publish a viewpoint that weakened themselves?
If less people are interested in a game due to this DRM, or due to the game just not being very good, that will also translate to less people interested in pirating it...
Simple, require manufacturers to release source code (and anything else required in order to build and run the source) once they are no longer willing to provide security updates. Someone else will pick up the slack and provide updates if enough people are still using the devices.
Why doesn't it? Do you not use the internet at all? If they can't issue new ipv4, then potential customers may only have ipv6 and be unable to access your website.
1, Any web based applications support it by default if the webserver does (which all common ones do), you can still do dual stack internally for legacy cruft... i certainly wouldnt deploy anything new that didnt support ipv6, how much legacy cruft do you have which requires ipx/spx or appletalk?
2, Routing hardware has been supporting ipv6 for a LONG time... Cisco introduced support for it in 2001 - 10 years ago, i would hardly call the current hardware "1st generation". Windows also gained production support in 2001 (XP), and other systems had it around the same time or earlier.
3, you can tunnel an ipv6 vpn over the ipv4 internet if your vpn endpoints dont have v6 connectivity
4, then your support staff and admins are poorly trained, there really is no excuse for anyone working in it to not have a working knowledge of ipv6.
This whole "not my problem" attitude is pure arrogance, and is the reason why ipv4 will become extremely costly for everyone. It doesn't take much effort to go dual stack, and if everyone had done that 10 years ago we wouldnt be having these problems now and ipv4 would be pretty much deprecated.
Migrating to another unix is likely to be a lot easier than migrating to windows... You will generally be running much the same software, and a lot of the configuration will be similar (tho without the gui tools).
I believe Apple are now supporting OSX server in non apple hardware, or at least within some hypervisor implementations... It kinda makes sense, since there's no point maintaining their own line of servers which was never much of a range, and were never big sellers.
Drugs and other medical research should not be performed by commercial entities in any case, there is far too much conflict of interest... For instance, it's far more profitable to keep someone sick and taking drugs than it is to cure them, so the research will be directed at temporarily alleviating symptoms rather than curing the underlying problem. Medical research should be carried out by charities, governments and other groups who's goal is improving people's health, not making a profit.
When it comes to other products there are different rules... Virtual products like software are protected by copyrights so your competitors cant just create a straight copy... So these and other physical products will take time for the competition to copy, giving you a head start. What you make of that head start is up to you, rip off the early adopters or earn yourself a reputation? If you earn a good enough reputation, people will still choose your product in future even when cheaper competitors become available as they will always be seen as cheap clones.
Also lets not forget, a lot of R&D is academic rather than commercial.
That assumes that they own all of the code, and that none of it was either contributed by a third party or is a derivative work of someone else's GPL code.
Personally i don't really like having 2 screens, i would rather have a single screen of the highest possible resolution. Although i absolutely cannot live without virtual desktops, i find it easier to make a quick keypress to flip between a large number of desktops than to keep moving my head sideways to look at additional screens.
That assumes these people even know anything to tell the feds... If the ringleaders are smart, and lets assume they are since they've convinced all these other guys to front their operation, then its unlikely these guys will know anything more than a made up alias on IRC and maybe the IP address they connected to IRC from, which was probably a tor exit node, or a compromised machine in china or similar.
You also make the assumption that these people are within areas that the FBI has jurisdiction over, what if they are located in china, russia or one of the various lawless african countries?
DOS was successful because it was cheap, and also ran on cheap hardware. Unix at the time was massively superior in every other way, as was the hardware it ran on but people couldn't justify or afford the cost. If Linux had come along earlier, it's likely that DOS would never have gained any traction at all.
However jailbreak users had a fix for this vulnerability available immediately right from the device itself, while non jailbreak users had to wait for Apple to provide one, and then must tether their device to a computer, download a large firmware file, reflash it and then restore all their settings to the device in order to be immune to the exploit.
Spoofing a MAC that is already in use works just fine, but you should assign an IP manually as DHCP will think you are the same user and give you the same IP..
If you spoof their MAC address and manually take their IP too, it will usually knock the other user offline and they probably wont have the skills or tools to work out what's happening.
The patent office should most certainly be liable for the costs incurred as a result of issuing a patent which is later found to be invalid... If they issue a patent which is later found invalid, then they have failed to do their job properly... Their own investigations should have found the same evidence, and thus refused to issue the patent in the first place. But due to the failure of the patent office not doing their job properly, the company holding the invalid patent incur costs defending it, the companies they attack incur costs defending themselves and ultimately invalidating the patent, and the court incurs costs and wastes time hearing the case. All of this mess, caused because the patent office didn't do its job properly in the first place - they should be liable for the costs.
Before nVidia supported Linux, there was good 2d support for earlier ati cards, s3 cards, cirrus logic and matrox... In terms of 3d, the 3dfx voodoo cards had pretty good support (they even provided glide drivers for linux), as did the matrox cards (they opened up their drivers, and the open ones surpassed the closed ones fairly quickly). ATI i don't especially like, not only did they ignore linux users, they also have traditionally provided very buggy drivers for windows too... On the other hand, AMD have always been good to the community, and they now own ATI so I have no qualms about using their cards today. A few years ago i would not have even considered buying an ATI card, however my 2 most recent videocard purchases have been from them, and it's good to know that the open drivers will continue to support these cards long after the closed ones have moved on.
What helps improve code quality, is not having deadlines... MS and other commercial organisations will ship code that isn't ready in order to meet deadlines, and put their developers under intense pressure to meet the deadlines causing them to cut corners. Linux has no such pressure, and developers are free to progress at their own pace. If something isn't ready, it doesn't get included, or gets partitioned off in the staging area with big warnings attached.
Another issue is that of visibility. If you're working in a big company on a large software project, its unlikely your contributions will even be acknowledged publicly, and conversely a failure if your code is unlikely to be directly blamed on you. With Linux however, the code you submit will have your name attached to it forever. So while submitting good code makes good publicity for you, submitting bad code earns you a reputation for writing bad code.
Slashdot Mirror
I have a mid 2010 macbook pro, it has the nvidia graphics and is running lion... It doesn't crash every 5 minutes, and has been up since the time i actually installed lion about 5 days ago.
Some 6 years ago i had a laptop with a 1024x768 internal screen which i carried round with me, and a 1280x1024 screen on my desk to which the laptop was connected whenever i was in the office... It ran linux, and worked perfectly.
Your problem actually sounds like the opposite of the traditional X11 configuration problem...
These days, the system tries to detect the capabilities of the monitor connected to it, whereas back in the days with linux you had to tell the system what capabilities your monitor had.
The problem is when things go wrong with the auto detection and people have forgotten how to manually override things...
Over 10 years ago, i had similar problems to yours but with windows, linux gave me no problems at all because it simply did what it was told and didn't try to be too smart.
More recently intact, i have a TV set that can do 1080p but doesn't seem to advertise the fact properly... Some devices work with it, some don't... I can't get OSX or Windows to talk 1080p to it, and neither will Linux by default but if i manually modify the X11 config it will... I have no idea how to make the necessary changes under OSX/Windows.
Out of interest, what were you trying to get the systems "joined up and working" with?
If it was an Active Directory environment then of course it would be more difficult to join anything non windows to it, that's how it's designed, so MS can claim "support" for joining non windows systems, but intentionally make it as difficult as possible to discourage you from using such systems.
Also the biggest problem with AD is security, get yourself an internal pen test and give them just a single ethernet socket to get started... If they're remotely competent they will have domain admin access before lunchtime.
Linux admins are not so much cheaper, as the general standard of windows admins is lower...
For equivalent levels of competence the price is about the same (and such people are generally able to use the other system to some level too), "cheaper" only comes around because there are lots of people with virtually no knowledge whatsoever calling themselves windows admins.
If you let everybody speak, and let everybody listen, the truth will be known.
However, the mass media is controlled by a very small group... While everyone may be able to speak, only the mass media will be listened to by any significant proportion of people and thus their agendas are furthered and everything else ignored.
If someone were to put up their own website explaining their side, how would anyone even learn of the existence of that site?
There is no way to be heard without money and power, and the only way to get money and power is to be a part of the current system and thus have a vested interest in maintaining the status quo.
The vast majority believe what they hear on the media, and never bother to question it... If they heard an alternative viewpoint they might believe that too, but why would those who control the media ever publish a viewpoint that weakened themselves?
But how about in a data center, where the heat is generated but not wanted...
If less people are interested in a game due to this DRM, or due to the game just not being very good, that will also translate to less people interested in pirating it...
Simple, require manufacturers to release source code (and anything else required in order to build and run the source) once they are no longer willing to provide security updates. Someone else will pick up the slack and provide updates if enough people are still using the devices.
Why doesn't it? Do you not use the internet at all?
If they can't issue new ipv4, then potential customers may only have ipv6 and be unable to access your website.
1, Any web based applications support it by default if the webserver does (which all common ones do), you can still do dual stack internally for legacy cruft... i certainly wouldnt deploy anything new that didnt support ipv6, how much legacy cruft do you have which requires ipx/spx or appletalk?
2, Routing hardware has been supporting ipv6 for a LONG time... Cisco introduced support for it in 2001 - 10 years ago, i would hardly call the current hardware "1st generation". Windows also gained production support in 2001 (XP), and other systems had it around the same time or earlier.
3, you can tunnel an ipv6 vpn over the ipv4 internet if your vpn endpoints dont have v6 connectivity
4, then your support staff and admins are poorly trained, there really is no excuse for anyone working in it to not have a working knowledge of ipv6.
This whole "not my problem" attitude is pure arrogance, and is the reason why ipv4 will become extremely costly for everyone. It doesn't take much effort to go dual stack, and if everyone had done that 10 years ago we wouldnt be having these problems now and ipv4 would be pretty much deprecated.
Migrating to another unix is likely to be a lot easier than migrating to windows... You will generally be running much the same software, and a lot of the configuration will be similar (tho without the gui tools).
I believe Apple are now supporting OSX server in non apple hardware, or at least within some hypervisor implementations...
It kinda makes sense, since there's no point maintaining their own line of servers which was never much of a range, and were never big sellers.
Drugs and other medical research should not be performed by commercial entities in any case, there is far too much conflict of interest... For instance, it's far more profitable to keep someone sick and taking drugs than it is to cure them, so the research will be directed at temporarily alleviating symptoms rather than curing the underlying problem.
Medical research should be carried out by charities, governments and other groups who's goal is improving people's health, not making a profit.
When it comes to other products there are different rules... Virtual products like software are protected by copyrights so your competitors cant just create a straight copy... So these and other physical products will take time for the competition to copy, giving you a head start.
What you make of that head start is up to you, rip off the early adopters or earn yourself a reputation? If you earn a good enough reputation, people will still choose your product in future even when cheaper competitors become available as they will always be seen as cheap clones.
Also lets not forget, a lot of R&D is academic rather than commercial.
That assumes that they own all of the code, and that none of it was either contributed by a third party or is a derivative work of someone else's GPL code.
Personally i don't really like having 2 screens, i would rather have a single screen of the highest possible resolution. Although i absolutely cannot live without virtual desktops, i find it easier to make a quick keypress to flip between a large number of desktops than to keep moving my head sideways to look at additional screens.
For non commercial use... A company system would be used for commercial uses, and thus wouldn't be valid under these terms.
That assumes these people even know anything to tell the feds...
If the ringleaders are smart, and lets assume they are since they've convinced all these other guys to front their operation, then its unlikely these guys will know anything more than a made up alias on IRC and maybe the IP address they connected to IRC from, which was probably a tor exit node, or a compromised machine in china or similar.
You also make the assumption that these people are within areas that the FBI has jurisdiction over, what if they are located in china, russia or one of the various lawless african countries?
Unfortunately, IE6 is big enough that if a site doesn't work with it, the site is blamed rather than the browser.
DOS was successful because it was cheap, and also ran on cheap hardware. Unix at the time was massively superior in every other way, as was the hardware it ran on but people couldn't justify or afford the cost. If Linux had come along earlier, it's likely that DOS would never have gained any traction at all.
However jailbreak users had a fix for this vulnerability available immediately right from the device itself, while non jailbreak users had to wait for Apple to provide one, and then must tether their device to a computer, download a large firmware file, reflash it and then restore all their settings to the device in order to be immune to the exploit.
Spoofing a MAC that is already in use works just fine, but you should assign an IP manually as DHCP will think you are the same user and give you the same IP..
If you spoof their MAC address and manually take their IP too, it will usually knock the other user offline and they probably wont have the skills or tools to work out what's happening.
What about the traffic going over the network? That's now open to interception by anyone within range...
Also its not hard to spoof a MAC address.
The patent office should most certainly be liable for the costs incurred as a result of issuing a patent which is later found to be invalid...
If they issue a patent which is later found invalid, then they have failed to do their job properly... Their own investigations should have found the same evidence, and thus refused to issue the patent in the first place.
But due to the failure of the patent office not doing their job properly, the company holding the invalid patent incur costs defending it, the companies they attack incur costs defending themselves and ultimately invalidating the patent, and the court incurs costs and wastes time hearing the case. All of this mess, caused because the patent office didn't do its job properly in the first place - they should be liable for the costs.
Before nVidia supported Linux, there was good 2d support for earlier ati cards, s3 cards, cirrus logic and matrox... In terms of 3d, the 3dfx voodoo cards had pretty good support (they even provided glide drivers for linux), as did the matrox cards (they opened up their drivers, and the open ones surpassed the closed ones fairly quickly).
ATI i don't especially like, not only did they ignore linux users, they also have traditionally provided very buggy drivers for windows too... On the other hand, AMD have always been good to the community, and they now own ATI so I have no qualms about using their cards today.
A few years ago i would not have even considered buying an ATI card, however my 2 most recent videocard purchases have been from them, and it's good to know that the open drivers will continue to support these cards long after the closed ones have moved on.
What helps improve code quality, is not having deadlines...
MS and other commercial organisations will ship code that isn't ready in order to meet deadlines, and put their developers under intense pressure to meet the deadlines causing them to cut corners.
Linux has no such pressure, and developers are free to progress at their own pace. If something isn't ready, it doesn't get included, or gets partitioned off in the staging area with big warnings attached.
Another issue is that of visibility. If you're working in a big company on a large software project, its unlikely your contributions will even be acknowledged publicly, and conversely a failure if your code is unlikely to be directly blamed on you.
With Linux however, the code you submit will have your name attached to it forever. So while submitting good code makes good publicity for you, submitting bad code earns you a reputation for writing bad code.