diff options
Diffstat (limited to 'sag-0.6.1-www/Invisible/sag-0.6/node54.html')
| -rw-r--r-- | sag-0.6.1-www/Invisible/sag-0.6/node54.html | 78 |
1 files changed, 78 insertions, 0 deletions
diff --git a/sag-0.6.1-www/Invisible/sag-0.6/node54.html b/sag-0.6.1-www/Invisible/sag-0.6/node54.html new file mode 100644 index 0000000..b4fa706 --- /dev/null +++ b/sag-0.6.1-www/Invisible/sag-0.6/node54.html @@ -0,0 +1,78 @@ +<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> +<!--Converted with LaTeX2HTML 96.1-h (September 30, 1996) by Nikos Drakos (nikos@cbl.leeds.ac.uk), CBLU, University of Leeds --> +<HTML> +<HEAD> +<TITLE>Partitioning schemes</TITLE> +<META NAME="description" CONTENT="Partitioning schemes"> +<META NAME="keywords" CONTENT="sag"> +<META NAME="resource-type" CONTENT="document"> +<META NAME="distribution" CONTENT="global"> +<LINK REL=STYLESHEET HREF="sag.css"> +</HEAD> +<BODY LANG="EN" > + <A NAME="tex2html994" HREF="node55.html"><IMG WIDTH=37 HEIGHT=24 ALIGN=BOTTOM ALT="next" SRC="./next_motif.gif"></A> <A NAME="tex2html992" HREF="node53.html"><IMG WIDTH=26 HEIGHT=24 ALIGN=BOTTOM ALT="up" SRC="./up_motif.gif"></A> <A NAME="tex2html986" HREF="node53.html"><IMG WIDTH=63 HEIGHT=24 ALIGN=BOTTOM ALT="previous" SRC="./previous_motif.gif"></A> <A NAME="tex2html996" HREF="node1.html"><IMG WIDTH=65 HEIGHT=24 ALIGN=BOTTOM ALT="contents" SRC="./contents_motif.gif"></A> <A NAME="tex2html997" HREF="node114.html"><IMG WIDTH=43 HEIGHT=24 ALIGN=BOTTOM ALT="index" SRC="./index_motif.gif"></A> <BR> +<B> Next:</B> <A NAME="tex2html995" HREF="node55.html">Space requirements</A> +<B>Up:</B> <A NAME="tex2html993" HREF="node53.html">Allocating disk space</A> +<B> Previous:</B> <A NAME="tex2html987" HREF="node53.html">Allocating disk space</A> +<BR> <P> +<H2><A NAME="SECTION005101000000000000000">Partitioning schemes</A></H2> +<P> + It is not easy to partition a disk in the best possible way. + Worse, there is no universally correct way to + do it; there are too many factors involved. +<P> + The traditional way is to have a (relatively) small root + filesystem, which contains <tt>/bin</tt><A NAME="1776"> </A>, <tt>/etc</tt><A NAME="1778"> </A>, <tt>/dev</tt><A NAME="1780"> </A>, + <tt>/lib</tt><A NAME="1782"> </A>, <tt>/tmp</tt><A NAME="1784"> </A>, and other stuff that is needed to get the + system up and running. This way, the root filesystem (in its + own partition or on its own disk) is all that is needed to bring + up the system. The reasoning is that if the root filesystem is + small and is not heavily used, it is less likely to become + corrupt when the system crashes, and you will therefore find it + easier to fix any problems caused by the crash. Then you create + separate partitions or use separate disks for the directory tree + below <tt>/usr</tt><A NAME="1786"> </A>, the users' home directories (often under + <tt>/home</tt><A NAME="1788"> </A>), and the swap space. Separating the home + directories (with the users' files) in their own partition makes + backups easier, since it is usually not necessary to backup + programs (which reside below <tt>/usr</tt><A NAME="1790"> </A>). In a networked + environment it is also possible to share <tt>/usr</tt><A NAME="1792"> </A> among several + machines (e.g., by using NFS), thereby reducing the total disk + space required by several tens or hundreds of megabytes times + the number of machines. +<P> + The problem with having many partitions is that it splits the + total amount of free disk space into many small pieces. + Nowadays, when disks and (hopefully) operating systems are + more reliable, many people prefer to have just one partition + that holds all their files. On the other hand, it can be less + painful to back up (and restore) a small partition. +<P> + For a small hard disk (assuming you don't do kernel + development), the best way to go is probably to have just one + partition. For large hard disks, it is probably + better to have a few large partitions, just in case + something does go wrong. (Note that `small' and `large' are + used in a relative sense here; your needs for disk space + decide what the threshold is.) +<P> + If you have several disks, you might wish to have the root + filesystem (including <tt>/usr</tt><A NAME="1794"> </A>) on one, and the users' home + directories on another. +<P> + It is a good idea to be prepared to experiment a bit with + different partitioning schemes (over time, not just while + first installing the system). This is a bit of work, since it + essentially requires you to install the system from scratch + several times, but it is the only way to be sure you do it right. +<P> +<HR><A NAME="tex2html994" HREF="node55.html"><IMG WIDTH=37 HEIGHT=24 ALIGN=BOTTOM ALT="next" SRC="./next_motif.gif"></A> <A NAME="tex2html992" HREF="node53.html"><IMG WIDTH=26 HEIGHT=24 ALIGN=BOTTOM ALT="up" SRC="./up_motif.gif"></A> <A NAME="tex2html986" HREF="node53.html"><IMG WIDTH=63 HEIGHT=24 ALIGN=BOTTOM ALT="previous" SRC="./previous_motif.gif"></A> <A NAME="tex2html996" HREF="node1.html"><IMG WIDTH=65 HEIGHT=24 ALIGN=BOTTOM ALT="contents" SRC="./contents_motif.gif"></A> <A NAME="tex2html997" HREF="node114.html"><IMG WIDTH=43 HEIGHT=24 ALIGN=BOTTOM ALT="index" SRC="./index_motif.gif"></A> <BR> +<B> Next:</B> <A NAME="tex2html995" HREF="node55.html">Space requirements</A> +<B>Up:</B> <A NAME="tex2html993" HREF="node53.html">Allocating disk space</A> +<B> Previous:</B> <A NAME="tex2html987" HREF="node53.html">Allocating disk space</A> +<P><ADDRESS> +<I>Lars Wirzenius <BR> +Sat Nov 15 02:32:11 EET 1997</I> +</ADDRESS> +</BODY> +</HTML> |