I've been in an environment where we we had a lot of power failures (and we had a faulty UPS that took a few weeks to get replaced). Whenever we lost power and then regained it, the 3 or 4 NT boxes would come up again, occasionally run CHKDSK automatically, fix anything, and boot up normally. The Linux box (RH 5.1) would need fsck run on it every time, and on one occasion, a power failure *while* fsck was running trashed the disk quite badly, requiring two or three hours of work to get the whole lot working again. NT's journalling file system is actually damn reliable, and on a decent machine, the whole system can be quite reliable.
NT doesn't need Samba because it already has SMB built in. Samba is great if you would like to make files on a Unix box easily available to Windows clients. NT is great if you need permissions on the shared files. Stability isn't a problem with NT if you have decent hardware and NT is properly set up.In a large organisation, the file security is worth the cost of a bigger machine and NT.
It's all very well setting up multiple shares for each, but we have a situation where we have an NT server with about 50GB of files, 450 shares (each with permissions), and thousands of directories under those shares, most of which have specific permissions granted to one or more groups or individuals. To allow someone to access a particular directory, I need just add them to the appropriate group.
For example: I have a "Budgets" share. Under Budgets are directories for 1997, 1998, 1999 and 2000. Under 1999 there is a separate directory for each of 20 business units. Under the "Networks" business unit directory are 10 subdirectories for each of the departments in Networks. Each departmental manager needs R/W access to his departmental directory. The BU manager needs R/W access to all the departmental directories, and the IT director needs R access to the lot. The Finance group needs R/W access to all the BU directories. The Management team needs R access to everything. Everyone else needs List access to the directories. Certain people may need specific access to particular files anywhere in that directory structure.
I don't think you can get that functionality with Unix and Samba, whereas it's trivial with NT.
Graeme
Screw Intel? No thanks. Down with AMD.
on
New Intel Celerons
·
· Score: 1
Well, I've had a K6-2 for about three months now (333 overclocked to 350), and it only crashes in one game (Jane's WWII Fighters), and runs continuously otherwise. I run Win98, occasionally Linux, with a variety of applications, including Bryce 3D, photo-editing packages, games etc. Prior to the K6-2, I had a K6-200 overclocked to 225, and that never caused problems either.
Slashdot Mirror
Nuclear cars? There's already been one, by Ford, I think. Worked well, but it was shelved because of concerns about the waste.
I've been in an environment where we we had a lot of power failures (and we had a faulty UPS that took a few weeks to get replaced). Whenever we lost power and then regained it, the 3 or 4 NT boxes would come up again, occasionally run CHKDSK automatically, fix anything, and boot up normally. The Linux box (RH 5.1) would need fsck run on it every time, and on one occasion, a power failure *while* fsck was running trashed the disk quite badly, requiring two or three hours of work to get the whole lot working again. NT's journalling file system is actually damn reliable, and on a decent machine, the whole system can be quite reliable.
NT doesn't need Samba because it already has SMB built in. Samba is great if you would like to make files on a Unix box easily available to Windows clients. NT is great if you need permissions on the shared files. Stability isn't a problem with NT if you have decent hardware and NT is properly set up.In a large organisation, the file security is worth the cost of a bigger machine and NT.
It's all very well setting up multiple shares for each, but we have a situation where we have an NT server with about 50GB of files, 450 shares (each with permissions), and thousands of directories under those shares, most of which have specific permissions granted to one or more groups or individuals. To allow someone to access a particular directory, I need just add them to the appropriate group.
For example: I have a "Budgets" share. Under Budgets are directories for 1997, 1998, 1999 and 2000. Under 1999 there is a separate directory for each of 20 business units. Under the "Networks" business unit directory are 10 subdirectories for each of the departments in Networks. Each departmental manager needs R/W access to his departmental directory. The BU manager needs R/W access to all the departmental directories, and the IT director needs R access to the lot. The Finance group needs R/W access to all the BU directories. The Management team needs R access to everything. Everyone else needs List access to the directories. Certain people may need specific access to particular files anywhere in that directory structure.
I don't think you can get that functionality with Unix and Samba, whereas it's trivial with NT.
Graeme
Well, I've had a K6-2 for about three months now (333 overclocked to 350), and it only crashes in one game (Jane's WWII Fighters), and runs continuously otherwise. I run Win98, occasionally Linux, with a variety of applications, including Bryce 3D, photo-editing packages, games etc. Prior to the K6-2, I had a K6-200 overclocked to 225, and that never caused problems either.
Graeme