My understanding is the price on bits needs to be high because those buying the bits are not buying the dead-wood editions; in other words, they have to (try to) make up the lost money from paper books on the electronic side.
FWIW, this has changed about jailbreaking. What you said used to be true on the 1.x series of iPhone software, where everything always ran as root. Therefore, a hole in libTIFF lead to (remote) root code execution. Starting with the 2.x series, Apple finally forced the restricted user account named Mobile to be used instead of root. That made it so now a libTIFF exploit *also* would require a privilege escalation exploit rolled inside; made things much harder. Starting around the 2.x software, the new way to jailbreak is by exploiting Apple's software update mechanism built into each device (Google: iBoot). This means that to jailbreak newer software/devices, one is required to attach the device to the computer first; the exploit is then done via USB.
Compute Shader for Shader Model 5.0, yes. However, starting with Catalyst 9.12 (December 2009) the HD48xx cards have driver support for CS for SM4.0. Regardless, afaik, no one is using either presently. Would be interesting to see a new physics engine that ran on this; PhysX for Compute Shaders I guess.
PC-EFI (an EFI emulation layer), FakeSMC, and other stuff based around boot-132; a lot of work from a guy named netkas but many people contributed to other drivers, etc. Rebel EFI included *at least* PC-EFI and boot-132-derived works; that also put them in direct violation of APSL, so they were screwed one way or another.
I'll second Mr. clone below me and suggest Process Explorer for when you have open handles in Windows. However, if you're looking for an equivalent to 'kill -9' for DOS, I do not think one exists.
I learned something new today too, apparently I was wrong about ls being equal to "list". Neat. Now, regarding ls being only two characters from the middle of the word, afaik that is purely historical, and comes from the early terminals where memory was a super-huge concern. That's why many of the basic commands dating from the early days of UNIX are so short - to conserve on typing and memory. As jimicus states later downthread, at this point changing it to something more sensible would cause more harm than good.
But in the end you're right, it's all what you've learned. To someone who has never used computers, they might expect "show files" to be a command, or something similar.
For anyone else following along, I found a handy DOS->bash chart here. For those reading wanting some bash-love, I highly recommend The Advanced Bash-Scripting Guide.
How about this? Man = MANual; ls = LiSt. What it sounds like you need is a Windows -> UNIX command line tutorial, not general help. After all, you learned "dir" from scratch at one point; to those of us who grew up using List (LS), a terse command like "dir" doesn't make a lot of sense either. And yes, I left out grep because there typically wasn't a great Windows equivalent.
FWIW, I grew up on DOS/Windows, so I do understand your points, and felt your pain. However, just like getting accustomed to DOS, once you get accustomed to BASH/ksh/csh/your-favorite-shell you'll wonder how you ever did without it.
Exactly - the clueless user is the target here. The technical users already know why they should jailbreak, and how to do it safely. Apple isn't worried about them because that crowd will always exist. However, they could leverage these worms to urge non-techies away from even thinking about jailbreaking. For instance, in the eyes of the average user, they could make jailbreaking synonymous with worms. Everybody here on/. knows jailbreak != worms, but what about everyone who reads Google News?
I think you will find that many smokers readily accept their responsibility as smokers. However, no smoker can stand the attitude often held by non-smokers. If I, as a smoker, am being considerate enough to not smoke near you, could you be considerate enough not to call me a filthy disgusting pig?
Isn't it also interesting that the fix is to, basically, un-jailbreak as soon as possible. If I were more of a conspiracy theorist, I would think Apple might have an interest in showing just how "bad" jailbreaking can be. Apple: See, if you jailbreak, you'll get a special phone worm!
I went and RTFA (and I'm not even new around here!). They have pretty much the same boot process as with Android devices. A read-only, signed firmware that passes control off to a R/W chip. I strongly recommend this link, but keep going and read all their security design docs. It is much more than just a small linux + Firefox + blahblah. Yeah, they're doing stuff any other manufacturer could be doing with linux, but this looks to be a very interesting set of designs and rules.
Geez..I dunno what it is but I have a soft spot for animals. I mean, I can watch a slasher movie where Freddie or Jason chainsaws 20+ teens into pieces, BUT...let them kick one dog....and I'm outta there.
Y'know, I feel the same way; I think it has to do with the concept of innocence. An animal - particularly a dog - only knows what it is taught. We as humans find something valuable in that. I think the reason we have an easier time with the slasher films is because we figure, well, they're just another group of dumbass people who probably put themselves into the bad situation -- the dog doesn't have that same choice.
What problem(s) did you have? I have an old HP P3-866 that happily accepted 9.04, but when trying to do anything to the hard drive, it errors out with problems creating a new ext4 partition. I can't figure out why it's happening.
Don't forget the lovely AppleMobileDevice service -- installed just in case you decide to buy an iPhone / iPod Touch at some point. Completely useless without one of said devices.
My main machine went from Vista SP0 to W7 beta1, then upgrades from beta1 thru various builds until final. Machine runs like a top, no problems.
MacBook got W7 beta1, and upgraded along the same paths up to final.
My third machine is running Vista SP1, and cannot - ever - run the upgrade to W7 final properly; it always dies somewhere in the process.
Now, the worst part to me is not that the second machine does not upgrade, but rather after the failure all it can tell me is "Upgrade was unsuccessful". Gee, thanks. Gonna tell me the sky is blue next?
I couldn't even guess what magic combination of things will make the upgrade process happy.
Slashdot Mirror
That's a hidden power of a low UID :-)
But why should bits honestly cost that much.
My understanding is the price on bits needs to be high because those buying the bits are not buying the dead-wood editions; in other words, they have to (try to) make up the lost money from paper books on the electronic side.
Also important: it supports userland mode-setting, *not* kernel-based mode-setting yet.
FWIW, this has changed about jailbreaking. What you said used to be true on the 1.x series of iPhone software, where everything always ran as root. Therefore, a hole in libTIFF lead to (remote) root code execution. Starting with the 2.x series, Apple finally forced the restricted user account named Mobile to be used instead of root. That made it so now a libTIFF exploit *also* would require a privilege escalation exploit rolled inside; made things much harder. Starting around the 2.x software, the new way to jailbreak is by exploiting Apple's software update mechanism built into each device (Google: iBoot). This means that to jailbreak newer software/devices, one is required to attach the device to the computer first; the exploit is then done via USB.
... hardware tessellation and compute shaders ...
Compute Shader for Shader Model 5.0, yes. However, starting with Catalyst 9.12 (December 2009) the HD48xx cards have driver support for CS for SM4.0. Regardless, afaik, no one is using either presently. Would be interesting to see a new physics engine that ran on this; PhysX for Compute Shaders I guess.
PC-EFI (an EFI emulation layer), FakeSMC, and other stuff based around boot-132; a lot of work from a guy named netkas but many people contributed to other drivers, etc. Rebel EFI included *at least* PC-EFI and boot-132-derived works; that also put them in direct violation of APSL, so they were screwed one way or another.
Damn Mongolians won't vote for me with the UN! :-)
(Yes, it's a Civ4 joke)
I'll second Mr. clone below me and suggest Process Explorer for when you have open handles in Windows. However, if you're looking for an equivalent to 'kill -9' for DOS, I do not think one exists.
I learned something new today too, apparently I was wrong about ls being equal to "list". Neat. Now, regarding ls being only two characters from the middle of the word, afaik that is purely historical, and comes from the early terminals where memory was a super-huge concern. That's why many of the basic commands dating from the early days of UNIX are so short - to conserve on typing and memory. As jimicus states later downthread, at this point changing it to something more sensible would cause more harm than good.
But in the end you're right, it's all what you've learned. To someone who has never used computers, they might expect "show files" to be a command, or something similar.
For anyone else following along, I found a handy DOS->bash chart here. For those reading wanting some bash-love, I highly recommend The Advanced Bash-Scripting Guide.
How about this? Man = MANual; ls = LiSt. What it sounds like you need is a Windows -> UNIX command line tutorial, not general help. After all, you learned "dir" from scratch at one point; to those of us who grew up using List (LS), a terse command like "dir" doesn't make a lot of sense either. And yes, I left out grep because there typically wasn't a great Windows equivalent.
FWIW, I grew up on DOS/Windows, so I do understand your points, and felt your pain. However, just like getting accustomed to DOS, once you get accustomed to BASH/ksh/csh/your-favorite-shell you'll wonder how you ever did without it.
Exactly - the clueless user is the target here. The technical users already know why they should jailbreak, and how to do it safely. Apple isn't worried about them because that crowd will always exist. However, they could leverage these worms to urge non-techies away from even thinking about jailbreaking. For instance, in the eyes of the average user, they could make jailbreaking synonymous with worms. Everybody here on /. knows jailbreak != worms, but what about everyone who reads Google News?
I think you will find that many smokers readily accept their responsibility as smokers. However, no smoker can stand the attitude often held by non-smokers. If I, as a smoker, am being considerate enough to not smoke near you, could you be considerate enough not to call me a filthy disgusting pig?
Isn't it also interesting that the fix is to, basically, un-jailbreak as soon as possible. If I were more of a conspiracy theorist, I would think Apple might have an interest in showing just how "bad" jailbreaking can be. Apple: See, if you jailbreak, you'll get a special phone worm!
I went and RTFA (and I'm not even new around here!). They have pretty much the same boot process as with Android devices. A read-only, signed firmware that passes control off to a R/W chip. I strongly recommend this link, but keep going and read all their security design docs. It is much more than just a small linux + Firefox + blahblah. Yeah, they're doing stuff any other manufacturer could be doing with linux, but this looks to be a very interesting set of designs and rules.
Geez..I dunno what it is but I have a soft spot for animals. I mean, I can watch a slasher movie where Freddie or Jason chainsaws 20+ teens into pieces, BUT...let them kick one dog....and I'm outta there.
Y'know, I feel the same way; I think it has to do with the concept of innocence. An animal - particularly a dog - only knows what it is taught. We as humans find something valuable in that. I think the reason we have an easier time with the slasher films is because we figure, well, they're just another group of dumbass people who probably put themselves into the bad situation -- the dog doesn't have that same choice.
Dropping support in this case means they are adding explicit code designed solely to prevent use on a processor the OS would otherwise work with.
Yeah, no kidding...
Signed, AMD
Seconded, big-time. I keep ClamWin installed in case I want to be really sure. :-)
What problem(s) did you have? I have an old HP P3-866 that happily accepted 9.04, but when trying to do anything to the hard drive, it errors out with problems creating a new ext4 partition. I can't figure out why it's happening.
Don't forget the lovely AppleMobileDevice service -- installed just in case you decide to buy an iPhone / iPod Touch at some point. Completely useless without one of said devices.
Standard disclaimer: YMMV, etc.
My main machine went from Vista SP0 to W7 beta1, then upgrades from beta1 thru various builds until final. Machine runs like a top, no problems.
MacBook got W7 beta1, and upgraded along the same paths up to final.
My third machine is running Vista SP1, and cannot - ever - run the upgrade to W7 final properly; it always dies somewhere in the process.
Now, the worst part to me is not that the second machine does not upgrade, but rather after the failure all it can tell me is "Upgrade was unsuccessful". Gee, thanks. Gonna tell me the sky is blue next?
I couldn't even guess what magic combination of things will make the upgrade process happy.
BTW, GO CARDS! Damn, they didn't even make the playoffs this year =(
Yeah, and didn't they get swept a couple years back by a certain Boston team? :-) (Sorry, I had to)
If I use Firefox, which Internet Explorer update do I need to install?
Replace Firefox with Honda Civic and Internet Explorer with Ford Focus.
"If I use Honda Civic, which Ford Focus update do I need [to install]?"
I refuse to believe, 3 years after seeing the original sig, that you are still making a movie :-)
+5 Rational. I wish I had mod points!
Hmm.. I've got an MCP61-based AMD system, and it also has PCI-Express 2.0. YMMV?