On 28/07/06 11:49, richard bown wrote:
<snip> I see now that Suse handles the disk partitions in a totally different way to Mandrake, where all the partitions are sequential, not as a sub-partition of one big one.
What you are seeing with SuSE is what is in the partition table. It is the same thing as you will see if you run fdisk -l. A partition table can have only 4 (primary) parititons in it, and these will always be named /dev/hd?1 through /dev/hd?4. If you have an extended partition, it will always be /dev/hd?4, even if you only have one primary partition on the drive. All logical drives will be /dev/hd?5 and up. This is the way it should be. Suppose, for example, that initially you created a primary partition on /dev/hda, then left some space unallocated on the drive, and finally created an extended partition with a couple of logical drives in it. Under sequential ordering, the partitions would be: primary -- /dev/hda1 extended -- /dev/hda2 logical -- /dev/hda3 and /dev/hda4 Now, if you create a partition in that unallocated space, what will it be labelled? /dev/hda5? It should properly be /dev/hda2, but that is already used. You cannot simply switch the extended partition to /dev/hda3, because now you have to relabel the logical partitions, and that screws up your /etc/fstab. As things are actually done, what you get is: primary -- /dev/hda1 (unallocated space) extended -- /dev/hda4 logical -- /dev/hda5 and /dev/hda6 Now when you create that new partition in the unallocated space, you will create /dev/hda2, and all that is necessary is to create a new line in /etc/fstab -- no mess, no bother. -- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com