Not long after the 10.5 release, I bought a MacBook 2.2 GHz to replace my PowerBook 867 MHz, which had obviously Mac OS X 10.5 preinstalled.
There seems to be a bug in 10.5, which wasn't in 10.4. It is impossible to configure static IPv6 addresses inside the System Preferences utility. Try it. The only way to use IPv6 in OS X 10.5, is to use radvd or configure them with ifconfig. I'd rather not ifconfig, because I use a lot of different network locations.:-/
No, it isn't. This is not related to the address space size of the hardware that's used. The reason why systems haven't switched to 64-bits is to remain compatible with current implementations. It would be quite evil if some binary thinks gettimeofday() is going to return a 32+32-bits structure, while in reality the kernel smacks a 64+32-bits structure in there.
I don't know much about Linux, but I do know that FreeBSD uses 64-bits time_t's on all architectures, except PowerPC and i386. You can easily see this by running the following commands:
FreeBSD box running i386:
$ date -j -f %s 233453453464 Failed conversion of ``233453453464'' using format ``%s''
FreeBSD box running amd64:
$ date -j -f %s 233453453464 Thu Nov 5 14:31:04 CET 9367
In 2038 almost nobody will use a 32-bits operating system on their PC's. Even if some people really *need* to do this, they can just change the time_t definition on their system and recompile everything. Nothing to see here. Move on.
Same problem here. The System Preferences tool doesn't really apply the IPv6 settings. Take a look at the ifconfig output in Terminal. Only lo0 has an IPv6 address.
As far as I know, it shouldn't make a difference. The only thing -g does, is adding debugging information (DWARF?) to the kernel's binary, stored in a seperate section. If you'd load that kernel, it would cost a lot more memory, but wouldn't slow down your system. The FreeBSD people aren't stupid, so what they do: they strip the debugging info before they install it. You load the kernel without the debugging information, but use the other one with kgdb.
I haven't used Windows lot lately, but when Vista got released I (legally) downloaded it from my school's website and installed it on my machine. I tinkered around with it. When I was done, I pressed Start -> Shutdown, which caused the machine to suspend. The machine immediately woke up when it entered its sleep. After a few seconds, smoke came out of my system and my only ATA disk in the machine caught fire.
I suspect that the on-board JMicron ATA controller can't properly handle suspend actions... Well, never mind. I bought a new S-ATA 300 disk and now everything is connected to Intel ICH-8 stuff. Too bad Vista doesn't handle AHCI properly, because now my disks run at S-ATA 150 when I boot Linux/FreeBSD/whatever.
Slashdot Mirror
Not long after the 10.5 release, I bought a MacBook 2.2 GHz to replace my PowerBook 867 MHz, which had obviously Mac OS X 10.5 preinstalled.
:-/
There seems to be a bug in 10.5, which wasn't in 10.4. It is impossible to configure static IPv6 addresses inside the System Preferences utility. Try it. The only way to use IPv6 in OS X 10.5, is to use radvd or configure them with ifconfig. I'd rather not ifconfig, because I use a lot of different network locations.
No, it isn't. This is not related to the address space size of the hardware that's used. The reason why systems haven't switched to 64-bits is to remain compatible with current implementations. It would be quite evil if some binary thinks gettimeofday() is going to return a 32+32-bits structure, while in reality the kernel smacks a 64+32-bits structure in there.
I don't know much about Linux, but I do know that FreeBSD uses 64-bits time_t's on all architectures, except PowerPC and i386. You can easily see this by running the following commands:
FreeBSD box running i386:
$ date -j -f %s 233453453464
Failed conversion of ``233453453464'' using format ``%s''
FreeBSD box running amd64:
$ date -j -f %s 233453453464
Thu Nov 5 14:31:04 CET 9367
In 2038 almost nobody will use a 32-bits operating system on their PC's. Even if some people really *need* to do this, they can just change the time_t definition on their system and recompile everything. Nothing to see here. Move on.
Same problem here. The System Preferences tool doesn't really apply the IPv6 settings. Take a look at the ifconfig output in Terminal. Only lo0 has an IPv6 address.
http://en.wikipedia.org/wiki/Robert_Watson_(computer_scientist) Robert Watson is a FreeBSD developer who spends a lot of time on the network stack and many other stuff. :-)
As far as I know, it shouldn't make a difference. The only thing -g does, is adding debugging information (DWARF?) to the kernel's binary, stored in a seperate section. If you'd load that kernel, it would cost a lot more memory, but wouldn't slow down your system. The FreeBSD people aren't stupid, so what they do: they strip the debugging info before they install it. You load the kernel without the debugging information, but use the other one with kgdb.
It seems you can enable msahci.sys after you've installed Vista: http://support.microsoft.com/kb/922976
I haven't used Windows lot lately, but when Vista got released I (legally) downloaded it from my school's website and installed it on my machine. I tinkered around with it. When I was done, I pressed Start -> Shutdown, which caused the machine to suspend. The machine immediately woke up when it entered its sleep. After a few seconds, smoke came out of my system and my only ATA disk in the machine caught fire. I suspect that the on-board JMicron ATA controller can't properly handle suspend actions... Well, never mind. I bought a new S-ATA 300 disk and now everything is connected to Intel ICH-8 stuff. Too bad Vista doesn't handle AHCI properly, because now my disks run at S-ATA 150 when I boot Linux/FreeBSD/whatever.