On Mon, 2003-12-01 at 18:39, Mark Ferlatte wrote: > Greg Folkert said on Mon, Dec 01, 2003 at 06:19:12PM -0500: > > root should only be enough to boot with... > > > > /etc = 45MB (with GConf taking 30MB of that) > > /bin = 3.5MB > > /sbin = 3MB > > /lib = 35MB > > /dev = 128KB > > /root = 15MB or so > > /proc = null > > /tmp = 50K or so (not a separate filesystem until multi-user/services) > > > > / should equal the sum of them ~ 100MB. Adding for growth a bit... > > That is why I say 200MB. > > > > These should all be separate partitions/drive/mountpoints > > /usr > > /usr/local > > /var > > /home > > /tmp > > /boot (personal pref) > > There are currently Debian packages which are needed at boot time which depend > upon datafiles kept in /usr. discover is one of them, there may be more. In > woody, therefor, a seperate /usr can cause problems. Does it gain you much?
You see, I have always had a separate /usr... never seen a problem yet.
Booting into "S" doesn't do the data discovery. That is what I am
getting at. "S" or "1" is maintenance mode. Everything you need to
maintain the boxen should be on "/" and that is all it should have. I
come from very heavy duty system, that they would get everything except
the root filesystem blotched out. Get massive upgrades "HOT" and then
I'd have to restore the filesystems. If I did not have everything I
needed to restore from a Remote Tape-Library... I was fscked. These
machine sometimes took hours to come up, with 32 Processors and 32GB of
Memory, Multiple Multi-terabyte filesystems (All with journal-ling)
Everything I needed was on /. Plus I could make a bootable tape or a
bootable CD or bootable DVD and still be inside (usually with frillz
added because I had room) 250MB. This was on AIX, HPUX, TRU64 (OSF/1),
etc...
So, now you understand why I always suggest 200MB(okay I have a 300MB /
filesystem).
> Why should /tmp be its own partition instead of symlinking /tmp -> /var/tmp?
/ and /var are machine critical. Let us remember I come from Huge
Enterprise setups. Let's just suppose You are a developer writing a
PL/SQL 300-way innerjoin. Those temporary files get written to /tmp.
With /tmp on "root" filesystem... oops there goes the machine
With /tmp on /var all logging goes away... among other things.
With /tmp its own filesystem... the PL/SQL fails "YEAH" that's what you
want.
> Is there any need for a /boot partition on modern hardware? Why do you like a
> seperate boot partition?
Yes. Simplicity. I use grub as a boot-loader.
My workstation menu.lst looks like:
---------------------------
timeout=5
default=0
fallback=1
root(hd0,0)
title 2.6.0-test9-20031123-k7
kernel /vmlinuz-2.6.0-test9-20031123-k7 ro root=/dev/hde2
initrd /initrd.img-2.6.0-test9-20031123-k7
title 2.4.22-20031108-k7
kernel /vmlinuz-2.4.22-20031108-k7 vga=791 ro root=/dev/hde2
initrd /initrd.img-2.4.22-20031108-k7
title 2.6.0-test9-1-386
kernel /vmlinuz-2.6.0-test9-1-386 ro root=/dev/hde2
initrd /initrd.img-2.6.0-test9-1-386
title 2.4.22-1-k7
kernel /vmlinuz-2.4.22-1-k7 vga=791 ro root=/dev/hde2
initrd /initrd.img-2.4.22-1-k7
title 2.4.21-20031012-k7
kernel /vmlinuz-2.4.21-20031012-k7 vga=791 ro root=/dev/hde2
initrd /initrd.img-2.4.21-20031012-k7
title 2.4.21-5-k7
kernel /vmlinuz-2.4.21-5-k7 vga=791 ro root=/dev/hde2
initrd /initrd.img-2.4.21-5-k7
---------------------------
If I had it included in "/" I'd have to add /boot to the front of every
line.
Plus it keeps me from having toooo many kernels installed, plus I can
make it read-only making it more difficult to change.
> I'm just curious as to the reasoning behind your partitioning scheme.
It's fine... I have used spreadsheets to map out things and I never have
come up with the perfect setup. Close... but not poifec
--
greg, [EMAIL PROTECTED]
REMEMBER ED CURRY! http://www.iwethey.org/ed_curry
signature.asc
Description: This is a digitally signed message part
