on Thu, Jun 05, 2003 at 12:25:56AM +0200, Frank Gevaerts ([EMAIL PROTECTED]) wrote:
> On Wed, Jun 04, 2003 at 05:51:12PM -0400, lists1 wrote:
> > Thanks to all.  I'm going to print out the Partitioning mini-faq, as it 
> > answers some other questions, and I'll use the examples for suid, remount, 
> > and others in fstab and elsewhere.  I did look at it last night, among a lot 
> > of other docs/posts, but the date and small partition sizes threw me a bit.  
> > I'm starting with a knoppix install (and moving to debian), and need bigger 
> > partitions, or the install just exits (at least that's what it does when it 
> > hits other problems).
> > 
> > I've adjusted as follows, but I doubt this will be the final setup:
> > 
> > /            1 GB   (may go a few hundred MB smaller)
> 
> if /usr, /home, /tmp and /var are separate, you can stop at 200-300 MB

Ditto.

> > /boot    100 MB  (Reiser FS requires larger size than ext2/3, according to    
> >                messages on suse installations, disallowing smaller sizes)

Then use another filesystem.  Ext3fs is fine for smaller partitions.
The journal file for ext3 is porportional to the size of the parition,
in Reiser, there's a dedicated 32MB overhead.  I consider the cutover to
be somewhere around 100-200 MB.

> > /opt       500  MB   hope this is big enough to squeeze knoppix on.

Nope.  You can't squish an 800 MB compressed file onto 500 MB.

> > /tmp        800 MB 

IMO grossly oversized.  100-200 MB should be sufficient, set explicit
use of temporary space for apps (usually graphics, video, or audio
editors, or databases and data manipulation tools) which have their own
extraordinary temporary space needs.  I've found this latter step
unnecessary with 256MB allocated for /tmp.  Most of my utilization (13%)
is the Reiserfs journal file.

> > /usr           3    GB

Good.

> > /var       2760 MB

Largeish, but OK.  Particularly OK if you justify it on useage needs.

> > /home  5240  MB
> > swap       500 MB  Is this enough for dealing with 700 MB iso images?

Yes.  See prior comments on swap sizing.  If you partition *multiple*
swap partitions (and you can do this after the fact), then you can
activate these as needed.  Swap needs memory for addressing, so adding
too much swap can actually eat into your memory utilization (someone
correct me if this is out of date info).  By creating multiple
partitions you can:

  - Size swap to fit your current needs.
  - Add additional partitions as you add RAM to your system.
  - Avoid repartitioning your system (painful).

> iso images are usually read/written sequentially, so they don't require
> much ram/swap
> 
> I might make /var a little smaller and /home a little bigger, but that
> depends on database/mail/webspace
> 
> If this is meant to be a _real_ mailserver, put /var/spool on a separate
> partition as well. For a personal/home server, this is probably not needed.

...for performance reasons.  Setting blocksize, and/or atime for a spool
can be particularly useful.  Not to mention having the partition be
isolated from other useful system stuff (say, /var/log, /var/cache, and
/var/lib) when it blows up.

> > Luckily, this box has the smallest drive.  Now if I could only squeeze 
> > debian/apache on to that 270 MB hard disk sitting in the corner for another 
> > box...
> 
> That should be easy. 270 MB is _huge_. You can get a basic install in
> about 100 MB. Add a few for apache, put in some swap, and you still have
> 100MB webspace left

Peace.

-- 
Karsten M. Self <[EMAIL PROTECTED]>        http://kmself.home.netcom.com/
 What Part of "Gestalt" don't you understand?
   Hollings:  bought, paid for, but couldn't deliver the CBDTPA:
     http://www.politechbot.com/docs/cbdtpa/hollings.s2048.032102.html


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to