[NTLUG:Discuss] Starting over.

[kbrannen@gte.net]

Scott Denlinger wrote:
> ... X started from the command line. No xdm, or kdm.

My favorite way. :-)

...
> 
> How much advantage does a journalling file system have over the 
> traditional ext2 file system? I was using ext3 on my last system (Reiser 
> before that, but that was problematic). If I do decide to use a 
> journalling file system, should I use it on my /var partition as well? 
> Or is there only an advantage to using it for boot/root partitions? My 
> /home partition is on a separate hard drive, so that will stay ext3.

In addition to the excellent advice given by Dan, I would add that it depends 
on how valuable your data is, and if you have an integrated UPS (a UPS that 
will send a signal the computer will notice and gracefully shut itself down to 
avoid corruption).  At work where I run databases (was Mysql, is now 
Postgres), a journaling file system is a big deal because of power issues 
(limited UPS plus no signal control and the boss won't buy a bigger/better 
UPS).  I've never had any problems with ReiserFS (used at home for several 
years now).  Recently started using ext3 at work; I was a bit learly about it, 
but we haven't had any problems yet. <crossing-fingers>

> 
> What size swap partition should I configure? Right now I have 96 MB of 
> RAM, but I may soon bump it up to 384 MB, which is the max. available 
> for my system board. I've read somewhere that the maximum swap partition 
> size which Linux can use is 128 MB. Is this true? I will be running a 
> MySQL database on this box, but it will basically be a learning tool for 
> me. It won't be for a production, enterprise-type database. Also no 
> graphics programming, or other CPU intensive stuff.

No.  I don't remember what is the max swap partition, but my box at work has a 
256M one and it is all used (a few times completely).  The old rule of thumb 
was 2x RAM of swap.  While not a useful rule, I think the correct size is what 
works for you and your needs; but for most of us, 1.5x RAM is a good starting 
point.  By the time you start getting to 1G RAM, then IMO there are no rules, 
but if you actually *need* that much RAM, you will probably have a big machine 
with plenty of disk, plus you (or a consultant you hire) will also have the 
expertise needed to determine a good swap size (as you'll probably be doing 
something at least semi-advanced. :-)  Oh, and if you have multiple disks (not 
partitions), *try* to spread your swap out evenly amongst the disks (1 swap 
area per disk to avoid thrashing).

Also, if you have an app that leaks memory badly, you'll want more swap space 
to compensate.  For example, I've finally traced my "memory loss" down to 
Mozilla caching stuff (pixmaps, fonts, and GC's) in the X server, but then 
never releasing those objects.  I've personally witnessed my X server taking 
up nearly 400M!  I compensate for that by have extra swap space.  BTW, if you 
search the Bugzilla site for mozilla.org, you'll find this is a known problem; 
  I hope a fix is found soon!  BTW2, there is a work-around to prevent 
reboots, it's inconvenient, but you can recover all the "lost" memory without 
rebooting.

HTH,
Kevin