I have a Pentium M in my notebook which can throttle 8 states
And the MBP has a Core Duo that can do that with both cores, independently. Configured right, the linux kernel controls it, with or without powernowd. OS X just does it by default, of course.
> I believe you say.. "A hoax" not "AN hoax".. correct me if I'm wrong.
You're wrong. At least, you're wrong if you live in a country where the official language is English, rather than American;)
I don't know what it should be in the US.
Yes, it probably will be easier. Unlike IPv4, IPv6 has have a strict hierachy - Large ISPs being allocated top-level blocks of addresses, giving smaller blocks to local ISPs, who in turn allocate even smaller blocks to end-users, rather than the current system which has no such restrictions. There's also the issue of using ethernet MAC addresses in the last section of the address, which would uniquely identify individual computers (and therefore attach your "fingerprint" to everything you do on the net).
http://www.ipv6.org/
http://rf.cx/rfc2373.html (refers to use of MAC addresses)
http://www.6bone.net/misc/case-for-ipv6.html (describes hierachical addressing ing IPv6 - page 30)
Slashdot Mirror
The open source HFS+ fsck and newfs are the same ones Mac OS X uses; obviously they do support HFSX.
And the MBP has a Core Duo that can do that with both cores, independently. Configured right, the linux kernel controls it, with or without powernowd. OS X just does it by default, of course.
Dunno about the US, but there's an educational discount on OS's here (.au). 10.3 is $129, as opposed to $229 for the non-discounted version.
> I believe you say.. "A hoax" not "AN hoax".. correct me if I'm wrong. You're wrong. At least, you're wrong if you live in a country where the official language is English, rather than American ;)
I don't know what it should be in the US.
Yes, it probably will be easier. Unlike IPv4, IPv6 has have a strict hierachy - Large ISPs being allocated top-level blocks of addresses, giving smaller blocks to local ISPs, who in turn allocate even smaller blocks to end-users, rather than the current system which has no such restrictions. There's also the issue of using ethernet MAC addresses in the last section of the address, which would uniquely identify individual computers (and therefore attach your "fingerprint" to everything you do on the net).
http://www.ipv6.org/
http://rf.cx/rfc2373.html (refers to use of MAC addresses)
http://www.6bone.net/misc/case-for-ipv6.html (describes hierachical addressing ing IPv6 - page 30)
This is impossible in HFS+. It preserves case, but is case-insensitive, so if you try to create a file called "bAR" it will overwrite "Bar".