From: Alan Mackenzie on
In comp.os.linux.setup Nico Kadel-Garcia <nkadel(a)gmail.com> wrote:
> On Apr 25, 12:44?pm, "David W. Hodgins" <dwhodg...(a)nomail.afraid.org>
> wrote:
>> On Sun, 25 Apr 2010 10:54:33 -0400, Ant <a...(a)zimage.comant> wrote:
>> > Thanks. Do I assume SCSI will still the same values too? How does
>> > one tell apart if you have both ATA and SCSI together (not that I
>> > will ever a SCSI device/card)?

>> Yes. ?Determining whether it's a scsi drive, ide, sata, or something
>> else can no longer be done based on the device name. ?Lower level
>> tools are required for that.

>> One thing to keep in mind, is that scsi drives have a limit of 15
>> partitions.

> What kind of crack monkey slaps more than 15 partitions on one drive?

Er, one like me? The recommendation used to be (perhaps still is)
setting up distinct partitions for things like /usr, /var, /home, /tmp,
/boot, /swap, and even /var/spool/mail, /usr/local, ..... You don't have
to be installing many installations before you hit that 15 partition
limit. Indeed with a near-infinite number of partitions available (63,
64?) who worries too much about eeking out their partitions?

With a limit of 15 partitions on a modern 1Tb drive, the average
partition size has got to be at least 66Gb. That's too big.

One answer is to build a kernel with /dev/hd?, and carry on happily using
/dev/hda and friends. Another is to use logical volume managers.

--
Alan Mackenzie (Nuremberg, Germany).

From: Wolfgang Draxinger on
Am Thu, 06 May 2010 09:57:10 GMT
schrieb anton(a)mips.complang.tuwien.ac.at (Anton Ertl):

> The reason I have separate partitions for /home and /usr/local is that
> I want to share them among different systems. E.g., I switched from
> RedHat to Fedora Core 1 to Gentoo to Debian while keeping /home and
> /usr/local the same. And for each new system I used a new partition.
> In the end I used the partitions up to number 15 (some of the primary
> partition numbers were unused).

Having /home separate is a good idea, but usually it ends up in a
different set of disks -- or in my case on a NAS -- anyway. When I was
talking about a single big /, then I was referring to the system's
installation, i.e. no separation into /var/, /usr/ and such.

In my university, when we were equipping the physics computer lab with
new machines, a lot of partitioning schemes were suggested. Well, the
first 5 testing installations I did, used the "big-root" scheme.
Apparently my colleagues enjoyed the reduction of
ENOSPACELEFT-during-installation headaches, that it's now used in the
installation proper. We did partition the disks though, so that we can
put alternate systems there later.


Wolfgang