[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Splitting Disk Space into partitions...
On Thu, 4 Jun 1998, Omer wrote:
> But, if you ask for optimal slicing,
>
> "/" 30 Mb | /etc includes a lot of config files
>
> "/var" 20 Mb | in case you will do print ||/&& mail spooling,
> | add disk space there, and cut from "/ur/local"
and then you'll need to clean out logs quite often (unless you don't have
too many logs). also, if you install redhat, it seems to install various
rpm-based fiels in /var/rpm, and so on. /var, by its nature, is a
partition where variable files (that come, grow and go) tend to be placed,
and thus 20MB is rather too little for that.
> "/usr" 150 Mb | and this include X + standard Xapps
you are not serious, i hope? again, at least with redhat,it places ALL
software in /usr, and thus whenyou upgrade and/or install RPM files,
that's where you need lots of space. on the other hand, if you usually
compile and install packages on your own, you'd be wise to place them in
/usr/local , to avoid clashes with your distribution, when you upgrade it.
> "/usr/local" 200 Mb | here KDE and WMaker and all other stuff
> | will go
i think the first advice, about putting them all as one partition, was
better. this is ofcourse unless these are 500MB that span accross more
then 1024 cylinders, and one wants to use lilo. in that case, i'd make one
root partition of 20-30MB in size, place /usr on the rest of the space,
and make /var, /tmp and similar directories become links to other
directories under /usr . the problem here is twofold:
1. making the switch is not trivial, since you might try to move files
that are open by various program (e.g. log files)
2. at least with redhat, it cannot cope with such things while you install
a new version - it has no /tmp, and thus many package installations
tend to fail... (unless you can create the links using relative paths,
and not full paths, as i stupidly did).
guy