> So, if you make it one big fat partition and your HD crashes, what do
> you do?
Usually, half the battle is just getting on the drive. If your OS is on a
FAT partition, then you can boot to a floppy and see the OS. This gives you
the ability to restore the registry file, metabases, problematic drivers,
etc. This is actually a practice recommended by IBM and one that has been
invaluable in dealing with Windows NT machines. It was so valuable, in fact,
that Microsoft built this capability right into the operating system so that
you can now, in Windows 2000, boot to a command prompt from the CD. So, as I
stated, it is no longer a viable reason to partition the system, which was
my point: I don't understand why he wants to partition the drive at all.
> Also, using Win2k you are probably running that most wholly
> of web servers IIS. Have your web stuff and OS stuff on the same
> partition is safe?? Hmm...
What difference does it make to security if your Web server and OS are on
the same partition? If you have one NTFS partition with everything installed
on that drive, it is no less safe than having two NTFS partitions with the
Web server installed on the second and the OS on the primary. In Windows NT,
security is handled at the file level, not the partition level.
> I think 8 GBs for your OS part is a little big, but you are on the
> right tract, IMHO. Plus, with all the new partitioning tools, if you
> run out of space on one, you can grow/shrink them.
I would not run any of those tools on a production server unless it was
absolutely necessary.
Benjamin S. Rogers
Web Developer, c4.net
Voice: (508) 240-0051
Fax: (508) 240-0057
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Structure your ColdFusion code with Fusebox. Get the official book at
http://www.fusionauthority.com/bkinfo.cfm
------------------------------------------------------------------------------
To unsubscribe, send a message to [EMAIL PROTECTED] with
'unsubscribe' in the body or visit the list page at www.houseoffusion.com
