diskadd c0b0t1d0

      fdisk        --   Is invoked to allow you to create a partition
      disksetup    --   Is run which helps you to do the following:
         * Surface Analysis   (not necessary for scsi drives)
         * Create the VTOC (Volume Table of Contents)
         * Write the bad track and bad sector table to the drive
         * Create the layout of slices on the new drive (up to 13 of them)
         * Use mkfs to make filesystems
         * Creates the lost+found directories automatically in any filesystem.
         * Creates the mount point directories.
         * Mounts the filesystems.
         * Updates the vfstab file.

   The 'disksetup' program walks you through all the steps via a simple
   series of questions.  It is well written and works smoothly.  You will
   need to know how many MB you want each slice to be, and what they
   will be called, and that's about it.

   *********************
   Some caveats:

      1)  UnixWare 7/OpenServer 6 uses a slice representation like 
          c0b0t0d0xx for almost everything that needs a drive named.

      2)  That naming has no partition information in it !!
          So you can't specify what partition you mean when you type
          c0b0t0d0s4 to refer to a slice.

      3)  The only way for UnixWare 7/OpenServer 6 to know what partition 
          contains slice 4, is for it to mark that partition active.

      4)  Thus you can only use one partition for filesystems on each
          hard drive.  And that one partition needs to be active for
          the system to know where to go.  The only exception is
          when you use a whole additional partition for one filesystem
          and no slices (call it /dev/dsk/c#b#t#d#p#  <-- no s).

      5)  In the active Unix partition, you can have 183 slices.  Diskadd
          only helps you create up to 13.  Any additional slices need to be
          hand created.  On the 2nd drive with scsi id=1, the slices would
          be 1 through b8 (because slices are listed in hex):

             /dev/rdsk/c0b0t1d0s1
            /dev/rdsk/c0b0t1d0s2
            /dev/rdsk/c0b0t1d0s3
                  ...
            /dev/rdsk/c0b0t1d0sb6
            /dev/rdsk/c0b0t1d0sb7     <--- Slice #'s are in hex, b7 = 183.

          I couldn't get 184 to work; so for now, I'll claim 183.

      6)  The situation where you would have more than one partition on
          another drive is where you need a raw partition for Database
          storage or you are using the trick of one filesystem taking up a
          whole partition with no slices in it.

<mschalit@pacbell.net>
gerberb@zenez.com