Why Partition a Hard Disk

[Chris Torek]

In article <1988Aug31.174144.1694 at utzoo.uucp> henry at utzoo.uucp
(Henry Spencer) writes:
[various reasons for particular partitions]
>If none of these considerations apply, the fewer the partitions the better.
>It is better to have one big free-space pool than a lot of little ones that
>can't help each other out when one gets low.

Agreed.  Lo:

mimsy% df
Filesystem    kbytes    used   avail capacity  Mounted on
/dev/ra0a      32795   12962   16553    44%    /
/dev/ra0d     368576  248822   82896    75%    /g
/dev/ra1d     369648  292440   40243    88%    /usr
/dev/ra2a      32795   12929   16586    44%    /tmp
/dev/ra2d     369648  315727   16956    95%    /ful
/dev/ra3h     434910  317324   74095    81%    /u
/dev/hp2h     234292  151032   59828    72%    /news
# ra1a is a backup copy of ra0a, and in a pinch can be used as a /tmp as well
# ra0b, ra1b, and ra2b are swap, ~30MB each

brillig% df
Filesystem    kbytes    used   avail capacity  Mounted on
/dev/hp0a      30823    8948   18793    32%    /
/dev/hp0d     332383     312  298832     0%    /bfd
/dev/hp1d     333463  267661   32455    89%    /usr
/dev/hp2a      30443    1698   25700     6%    /tmp
/dev/hp2d     333643  289715   10563    96%    /g
/dev/hp3h     395607  333135   22911    94%    /u
/dev/hp4h     395607   84214  271832    24%    /y
# hp1a is a backup of hp0a, as on mimsy
# likewise, hp0b, hp1b, and hp2b are swap, all ~30MB each
# `bfd' stands for Backup File Disk... really! :-)
# (and /g, /u, and /y have nothing to do with Mr. Harris)
-- 
In-Real-Life: Chris Torek, Univ of MD Comp Sci Dept (+1 301 454 7163)
Domain:	chris at mimsy.umd.edu	Path:	uunet!mimsy!chris