<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
<HTML>
<HEAD>
<META NAME="GENERATOR" CONTENT="SGML-Tools 1.0.9">
<TITLE>HOWTO: Multi Disk System Tuning: Appendix I: Example III: SPARC Solaris</TITLE>
<LINK HREF="Multi-Disk-HOWTO-30.html" REL=next>
<LINK HREF="Multi-Disk-HOWTO-28.html" REL=previous>
<LINK HREF="Multi-Disk-HOWTO.html#toc29" REL=contents>
</HEAD>
<BODY>
<A HREF="Multi-Disk-HOWTO-30.html">Next</A>
<A HREF="Multi-Disk-HOWTO-28.html">Previous</A>
<A HREF="Multi-Disk-HOWTO.html#toc29">Contents</A>
<HR>
<H2><A NAME="s29">29. Appendix I: Example III: SPARC Solaris</A></H2>
<P>
<!--
disk!example!server, industrial
-->
<P>The following section is the basic design used at work for a number of
Sun SPARC servers running Solaris 2.5.1 in an industrial development
environment. It serves a number of database and cad applications in
addition to the normal services such as mail.
<P>Simplicity is emphasized here so <CODE>/usr/lib</CODE> has not been split
off from <CODE>/usr</CODE>.
<P>This is the basic layout, planned for about 100 users.
<P>
<BLOCKQUOTE><CODE>
<PRE>
Drive: SCSI 0 SCSI 1
Partition Size (MB) Mount point Size (MB) Mount point
0 160 swap 160 swap
1 100 /tmp 100 /var/tmp
2 400 /usr
3 100 /
4 50 /var
5
6 remainder /local0 remainder /local1
</PRE>
</CODE></BLOCKQUOTE>
<P>Due to specific requirements at this place it is at times necessary to
have large partitions available on a short notice. Therefore drive 0 is
given as many tasks as feasible, leaving a large <CODE>/local1</CODE>
partition.
<P>This setup has been in use for some time now and found satisfactorily.
<P>For a more general and balanced system it would be better to swap <CODE>/tmp</CODE>
and <CODE>/var/tmp</CODE> and then move <CODE>/var</CODE> to drive 1.
<P>
<HR>
<A HREF="Multi-Disk-HOWTO-30.html">Next</A>
<A HREF="Multi-Disk-HOWTO-28.html">Previous</A>
<A HREF="Multi-Disk-HOWTO.html#toc29">Contents</A>
</BODY>
</HTML>
