I'd make a snarky comment about baseball players needing transportation too, but considering that they're all paid outrageous salaries for no measurable contribution to society...
Not quite. To my knowledge, Mac OS 9 and earlier apps could run in OS X by means of the "Classic" abstraction layer; in other words, OS X was emulating earlier APIs. Likewise, when Apple made the switch to x86 procs, they used a binary-translation layer called "Rosetta", that translated PowerPC instructions to x86 instructions.
XP Mode is very different from either of those. Quite simply, XP Mode is an extension of Virtual PC that allows an application to appear like it's running directly from the host OS, when in fact it is running under a guest OS. Because of this, you have a new, virtual system that needs to be secured, just like any other system.
Also, they're supposed to release the L4D SDK at the same time as the Survival Pack, which will let people make their own custom campaigns "discoverable via L4D's matchmaking system.
If that's the case, I'd suggest joining a campaign game already in progress; there's a good chance that the players will already be halfway through the campaign by the time you join.
And worst case scenario, just leave mid-game if you run out of time; the computer will take over for you.
You're missing the point entirely. You're focusing on whether or not the driver is supported in the first place. I'm focusing on who you blame for the driver being shitty.
The manufacturer is under no obligation to provide the drivers for a niche OS. They are under no obligation to provide you with specs; they sold you the hardware and the support for the OSes they claimed, nothing more. Consequential, it's not a "bad thing" if the manufacturer DOESN'T support Linux, because they didn't SELL you Linux support. If you want to make your own driver so that the hardware will work on Linux, good for you, community support is part of what makes Linux what it is. But that makes you solely responsible for the quality of your driver.
Which brings us back to the point I was driving at: driver related stability issues are the fault of whoever made the drivers. If nVidia's shitty (unsigned) display drivers cause instability in Windows, it's nVidia's fault. You don't get to blame Microsoft until they sign the shitty drivers or include them on the install disc, thereby endorsing them. Likewise, you don't get to blame stability issues caused by ATI's shitty drivers in Linux on Red Hat, unless they specifically included them in the distro. You just can't reasonably blame them for shitty drivers you get from a third party.
You know, I almost put this in my original post, but decided against it...
I don't want to hear any whiny "oh they didn't give us an documentation" bullshit, because it's just that: BULLSHIT. They are under no obligation to support Linux. If they don't believe supporting Linux would be worth the investment, they don't have to. Likewise, they are under no obligation to release the documentation. Most corporations would such documentation as something that could potentially help their competitors, should they get their hands on it.
Simply put, any given company has ZERO obligation to make their product what YOU want it to be; their only obligation is to make the product what they CLAIM it to be. If you feel otherwise, it's because you have some sort of misplaced sense of entitlement.
I'm sure that Microsoft would LOVE to take on that stance, if you just tell them that you'll absorb all the legal costs involved with FORCING every device manufacturer to comply.
Alternatively, they could just have Windows refuse to use drivers they haven't signed, instead of just giving a warning. I'm sure users would LOVE that...
It's a matter of who's claiming to support it. Just about every device manufacturer on the planet "supports" Windows. Therefore, if something goes wrong with the driver, it's THEIR fault, not Microsoft. Likewise, if they claim their product "supports" Linux, then it THEIR fault if the driver buggers up.
If, however, the manufacturer makes NO claims to supporting the OS, and the community makes their OWN drivers to "support" the device, crappy drivers are the fault of the community, not the manufacturer.
In the case of most hardware under Windows, it's the manufacturer supporting the OS, making the manufacturer responsible for crappy drivers.
In the case of most hardware under Linux, it's the Linux community supporting the harder, making the community responsible for crappy drivers.
The story the EFF is putting forward is actually incomplete and VERY misleading. The guy is being accused of a LOT of things; changing students grades, "jail breaking cell phones" (since when is THAT a crime?), massive copyright infringement, and harassment, to which the e-mail in question is related.
Considering all of THAT, data storage devices are practically MANDATORY for the warrant. And considering that iPods can, and frequently ARE, used as USB hard drives, they're fair game.
Also, we ARE talking about an iPod Touch, as mentioned in the second link in the/. story.
Your average copper thief isn't exactly a trained professional. Hell, most of the copper theft around where I live is down by transients who probably don't know a damned thing about cables other than that they can sell them.
Put a length of fiber and a length copper in front of them, don't let them see the ends, and they'll NEVER know the difference.
Or they built them, waited until they had a decent amount, and released them all at once, instead of having massive shortages like when they launched their LAST console...
Slashdot Mirror
I'd make a snarky comment about baseball players needing transportation too, but considering that they're all paid outrageous salaries for no measurable contribution to society...
Can it continue to download torrents and such while the computer is powered-down/in stand-by?
And yet you did...
Not quite. To my knowledge, Mac OS 9 and earlier apps could run in OS X by means of the "Classic" abstraction layer; in other words, OS X was emulating earlier APIs. Likewise, when Apple made the switch to x86 procs, they used a binary-translation layer called "Rosetta", that translated PowerPC instructions to x86 instructions.
XP Mode is very different from either of those. Quite simply, XP Mode is an extension of Virtual PC that allows an application to appear like it's running directly from the host OS, when in fact it is running under a guest OS. Because of this, you have a new, virtual system that needs to be secured, just like any other system.
Hate to nit-pick, but UTP means UNSHIELDED twisted pair.
So, yeah, how did that shielded unshielded twisted pair work out for ya?
Also, they're supposed to release the L4D SDK at the same time as the Survival Pack, which will let people make their own custom campaigns "discoverable via L4D's matchmaking system.
So, new maps are DEFINITELY on the way.
Uh, both the remaining campaigns WILL be introduced to Versus mode as part of the Survival Pack...
If that's the case, I'd suggest joining a campaign game already in progress; there's a good chance that the players will already be halfway through the campaign by the time you join.
And worst case scenario, just leave mid-game if you run out of time; the computer will take over for you.
You're missing the point entirely. You're focusing on whether or not the driver is supported in the first place. I'm focusing on who you blame for the driver being shitty.
The manufacturer is under no obligation to provide the drivers for a niche OS. They are under no obligation to provide you with specs; they sold you the hardware and the support for the OSes they claimed, nothing more. Consequential, it's not a "bad thing" if the manufacturer DOESN'T support Linux, because they didn't SELL you Linux support. If you want to make your own driver so that the hardware will work on Linux, good for you, community support is part of what makes Linux what it is. But that makes you solely responsible for the quality of your driver.
Which brings us back to the point I was driving at: driver related stability issues are the fault of whoever made the drivers. If nVidia's shitty (unsigned) display drivers cause instability in Windows, it's nVidia's fault. You don't get to blame Microsoft until they sign the shitty drivers or include them on the install disc, thereby endorsing them. Likewise, you don't get to blame stability issues caused by ATI's shitty drivers in Linux on Red Hat, unless they specifically included them in the distro. You just can't reasonably blame them for shitty drivers you get from a third party.
You know, I almost put this in my original post, but decided against it...
I don't want to hear any whiny "oh they didn't give us an documentation" bullshit, because it's just that: BULLSHIT. They are under no obligation to support Linux. If they don't believe supporting Linux would be worth the investment, they don't have to. Likewise, they are under no obligation to release the documentation. Most corporations would such documentation as something that could potentially help their competitors, should they get their hands on it.
Simply put, any given company has ZERO obligation to make their product what YOU want it to be; their only obligation is to make the product what they CLAIM it to be. If you feel otherwise, it's because you have some sort of misplaced sense of entitlement.
I'm sure that Microsoft would LOVE to take on that stance, if you just tell them that you'll absorb all the legal costs involved with FORCING every device manufacturer to comply.
Alternatively, they could just have Windows refuse to use drivers they haven't signed, instead of just giving a warning. I'm sure users would LOVE that...
It's a matter of who's claiming to support it. Just about every device manufacturer on the planet "supports" Windows. Therefore, if something goes wrong with the driver, it's THEIR fault, not Microsoft. Likewise, if they claim their product "supports" Linux, then it THEIR fault if the driver buggers up.
If, however, the manufacturer makes NO claims to supporting the OS, and the community makes their OWN drivers to "support" the device, crappy drivers are the fault of the community, not the manufacturer.
In the case of most hardware under Windows, it's the manufacturer supporting the OS, making the manufacturer responsible for crappy drivers.
In the case of most hardware under Linux, it's the Linux community supporting the harder, making the community responsible for crappy drivers.
The story the EFF is putting forward is actually incomplete and VERY misleading. The guy is being accused of a LOT of things; changing students grades, "jail breaking cell phones" (since when is THAT a crime?), massive copyright infringement, and harassment, to which the e-mail in question is related.
/. story.
Considering all of THAT, data storage devices are practically MANDATORY for the warrant. And considering that iPods can, and frequently ARE, used as USB hard drives, they're fair game.
Also, we ARE talking about an iPod Touch, as mentioned in the second link in the
Link to the full warrant affidavit: http://www.eff.org/files/filenode/inresearchBC/EXHIBIT-A.pdf
Are you saying that the elderly and/or disabled can AIM a gun?
...he apparently failed the save about 17 minutes before you were "in"...
GameStop #1942
Valley River Center
Valley River Center
Eugene OR, 97401 US
(541) 345-1022
Mon-Sat 10am-9pm, Sun 12pm-6pm*
GameStop #4545
Gateway Mall
3000 GATEWAY STREET
SPRINGFIELD OR, 97477 US
(541) 744-7844
Mon-Thu 10am-9pm, Fri-Sat 10am-10pm, Sun 11am-7pm*
PAL for the lose.
Err, not that I'D ever look at a torrent...
Considering the cases/boxes for PC games tend to be much larger than than for console games, I call bullshit.
Besides, why would someone shoplift when the torrent went up days or weeks before it hit the shelves?
I may or may not have bad news for him...
Your average copper thief isn't exactly a trained professional. Hell, most of the copper theft around where I live is down by transients who probably don't know a damned thing about cables other than that they can sell them.
Put a length of fiber and a length copper in front of them, don't let them see the ends, and they'll NEVER know the difference.
The cables are indeed both glass and copper. But only until you check.
OEM copies are supposed to be sold to system builders for use in a new system only; that's why they disable upgrade installations.
Well, at least the vowel ended up in the right place.
I hate unexpected vowel movements...
Or they built them, waited until they had a decent amount, and released them all at once, instead of having massive shortages like when they launched their LAST console...
So we can all see what a consumer whore you are?