Last I checked, the phrase "What's Happenin'" was strongly identified with Raj, Dwayne, and Rerun. Any patent lawyers in the house, that can help a brother out.
"Little did he know that the seeds were being planted for him and his future company to revolutionize the computer industry and electronic communications for businesses and consumers worldwide."
Bob Young sure thinks alot of himself. I hope that this was said by the "omniscient third person". Personally, I don't see how he's revolutionizing anything. In my eyes, he's just another greedy "Internet" millionaire making money on other people's work.
Religions abhorring murder is a relatively new development, brought about by the democratic and individualistic movements.
Take my word for it, if religions still wielded the powers they had in pre-democratic societies, they would gladly advocate murder. Of those who opposed them, the infidels.
That said, I have clients who use NT in mission citical systems with no problems. Some of the systems have never crashed. Of course, they do occassionally need to be rebooted because of service packs, etc. When this reboot need will end, who knows.
As for the other things it purportedly "sucks" for, most of my associates haven't had too many problems with any of those things.
I might suggest that you are not very good with NT. If I were as mean spirited as yourself.
2) You have very little control over where you go to find your libraries. Compare this to LD_LIBRARY_PATH where you can set exactly where you look for your libraries (thus giving you the ability to use different versions without harming each other).
The PATH evironment variable is used by NT to locate libraries when they are needed. This value can be changed for any process, allowing for multiple versions of libraries to be loaded. Of course, setting this up for system level DLLs, like ODBC, can be tricky at best. But, for things like the equivalent to libc, it's really easy. Just put "." as the first entry in the PATH.
How secure is this? Anyone with physical access can change the root password.
I can't believe that that's not possible in NT. After all, if somebody has physical access to a machine and can power-cycle it, you're beyond the protection that a password can give you anyway...
How are you beyond the protection a password can provide. Given an encrypted file system, what can one do? Turn it off? Smash the machine? Wouldn't the data security, if not the data itself, still be intact?
>4. No emergency repair disk > Ditto, especially Linux. >At least with Linux, if you don't make one at the start, all you have to do is download/copy a file onto a disk and you've got one made. RDISK.EXE is the tool used to create/update the emergency repair disk.
Slashdot Mirror
Last I checked, the phrase "What's Happenin'" was strongly identified with Raj, Dwayne, and Rerun. Any patent lawyers in the house, that can help a brother out.
"Little did he know that the seeds were being planted for him and his future company to revolutionize the computer industry and electronic communications for businesses and consumers worldwide."
Bob Young sure thinks alot of himself. I hope that this was said by the "omniscient third person". Personally, I don't see how he's revolutionizing anything. In my eyes, he's just another greedy "Internet" millionaire making money on other people's work.
Religions abhorring murder is a relatively new development, brought about by the democratic and individualistic movements.
Take my word for it, if religions still wielded the powers they had in pre-democratic societies, they would gladly advocate murder. Of those who opposed them, the infidels.
Wow, you sure are a mean spirited person.
That said, I have clients who use NT in mission citical systems with no problems. Some of the systems have never crashed. Of course, they do occassionally need to be rebooted because of service packs, etc. When this reboot need will end, who knows.
As for the other things it purportedly "sucks" for, most of my associates haven't had too many problems with any of those things.
I might suggest that you are not very good with NT. If I were as mean spirited as yourself.
2) You have very little control over where you go to find your libraries. Compare this to LD_LIBRARY_PATH where you can set exactly where you look for your libraries (thus giving you the ability to use different versions without harming each other).
The PATH evironment variable is used by NT to locate libraries when they are needed. This value can be changed for any process, allowing for multiple versions of libraries to be loaded. Of course, setting this up for system level DLLs, like ODBC, can be tricky at best. But, for things like the equivalent to libc, it's really easy. Just put "." as the first entry in the PATH.
How secure is this? Anyone with physical access can change the root password.
I can't believe that that's not possible in NT. After all, if somebody has physical access to a machine and can power-cycle it, you're beyond the protection that a password can give you anyway ...
How are you beyond the protection a password can provide. Given an encrypted file system, what can one do? Turn it off? Smash the machine? Wouldn't the data security, if not the data itself, still be intact?
>4. No emergency repair disk > Ditto, especially Linux. >At least with Linux, if you don't make one at the start, all you have to do is download/copy a file onto a disk and you've got one made. RDISK.EXE is the tool used to create/update the emergency repair disk.