On Tue, 3 Jun 2003, charlie wrote: > On Mon, 2 Jun 2003 10:20 pm, Wolfgang Bornath sent this :- > > Also supermount is still an issue - I disabled it and do much better > > than with it. > > Supermount is the first thing to go, always.
I second that commotion. Nice idea, but still not ready for prime time. :) As for partitioning, I agree that a separate /usr/local is wise if you plan on installing much from tarballs (and you might, like I do, use a symlink to point /opt at /usr/local as well, so the same partition is used for both purposes). I *invariably* go with a separate /var, and tend to prefer a large one (say, 1GB) if space is available, even if there is no webserver or such being run on the box; it protects against runaway logs filling up the / partition, and gives plenty of room for urpmi to cache RPMs when updates for large, interrelated subsystems such as KDE appear on the mirrors (which will expect to all be installed together). I also find that a "true" /tmp partition, as opposed to the default tmpfs pseudo-fs, can be a help on systems which have limited RAM available. I always keep /home separate, and tar up /etc and /var prior to each new upgrade-via-fresh-install, then incorporate the salient data from those dirs into the new files/tree of the new install carefully - as in many cases, especially in /etc, the file's formats/names/locations may differ slightly from those of the prior release (Apache2 comes to mind here), but there is always a correct place to put that data, *somewhere* ... ;) -- Bill Mullen [EMAIL PROTECTED] MA, USA RLU #270075 MDK 8.1 & 9.0 "Giving money and power to the government is like giving whiskey and car keys to teenage boys." - P.J. O'Rourke
Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
