On Mon, Mar 24, 2008 at 10:43:43AM -0700, Mark Srebnik wrote:
> 
> MarksU810:/home/archimark# df
> Filesystem           1K-blocks      Used Available Use% Mounted on
> /dev/hda2               264443    104306    146482  42% /
> tmpfs                   513468         0    513468   0% /lib/init/rw
> udev                     10240        68     10172   1% /dev
> tmpfs                   513468         0    513468   0% /dev/shm
> /dev/hda9             17884120    260700  16714948   2% /home
> /dev/hda8               381138     10310    351150   3% /tmp
> /dev/hda5              4806904   1719352   2843368  38% /usr
> /dev/hda6              2885780    408516   2330676  15% /var

 I've no issues with what Marius has said, but I'd like to add a
couple more things.

1. Having /home on a separate partition, and shared by all my
systems, is useful.  But, all my current systems are LFS or clfs, so
totally under my control.  On some of my more obscure architectures
I've loaded debian or ubuntu as a first stage, and my desktop
settings sometimes broke those.  Among other things, user and group
IDs have given me problems in the past - of course, you can go with
the group IDs you have in debian, if that helps.

2. I agree with Marius that you have too many separate filesystems.
When I started LFS on an old machine dedicated to testing, I went
over the top in defining filesystems - even /usr/local was separate
(plus, of course, 2 or 3 spare filesystems for future builds).  The
big problem with that is that programs are normally linked to libc -
if you upgrade a second system to a newer glibc, you probably
prevent all the other partitions from running in that system.  Also,
LFS itself installs to /var so you can't really share that.

 Old 'nix hands used to recommend putting /usr separately, but for
most people it doesn't give any advantage.  I note you had a tiny '/'
in the above example, but without special measures it still has to be
mounted r/w so you don't gain anything.

 /var isn't normally used for a lot on a desktop (unless debian uses
/var/cache for man pages or package management).  Similarly /tmp,
unless you want to use that for building packages (and if you do, it
will be cleared out at reboot by the LFS bootscripts).  On a server
I'd perhaps separate /var (swings and roundabouts - when any active
filesystem fills up to 100%, unpleasant things happen).

 Actually, you could probably get a long way into BLFS using
/dev/hda6 - more space is always good, and on some of my boxes I
have to build in /home for things like boost which is somewhat
bloated, but until recently I've managed ok in 3GB.

ĸen
-- 
das eine Mal als Tragödie, das andere Mal als Farce
-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page

Reply via email to