Thick_guy_9, your advice applies either less or no more to Solaris 10, which fixes many of the issues you describe:
- You can (and need) to install S10 from CD #1
- Solaris partition id has changed from 0x82 to 0xbf, no more clash exists
-
http://docs.sun.com/app/docs/doc/817...gbagb1b?a=view is accurately explaining how to install, other sites may still help too.
- Just to clarify:
- Solaris is calling partitions or fdisk partitions the thing everyone in the PC world is simply calling a partition (four primaries: p1, p2, p3, p4 + extended: p0:c, p0:d, ... )
- Slices are subdivisions of the solaris fdisk partitions (s0, s1 ... s7), they are sometimes called partitions too in the documentation, but the meaning is always explained.
When Solaris run on SPARC hardware, there is no fdisk underlying partition and the slices span the whole disk.
On x86/x64, the Solaris fdisk partition can have up to 16 slices.
Linux is making no distinction between Solaris slices and extended partitions logical volumes, it is just giving them consecutive numbers as soon as it discovers them at boot (hda5, hda6, hda7, ...).
This can prove very annoying should a previously primary partition is promoted to Solaris while an extended partition is already existing on a numerically superior partition, as all the linux numbering is shifted and the fstab is broken.
This problem doesn't exists with solaris where the partition naming is consistently pointing to the target devices.
