On Sat, Oct 20, 2007 at 08:26:33PM -0400, Douglas A. Tutty wrote: > OK, so one stock that works, one custom that works, room for a new > custom to test, and room for a new stock to test. That's room for four > kernels, their initrds, and their modules in lib. So how big a / does > that mean if the usual separate filesystems are used? > > And how big does that make /boot should someone need a separate /boot > (e.g. / is on LVM over raid1 with /boot on a separate raid1)? Depends also on the initrd creator used: ls -l /boot | grep 'initrd\|vmlinuz' -rw------- 1 root root 1109525 2007-08-17 18:08 initrd.img-2.6.18-5-686 -rw------- 1 root root 1231769 2007-08-06 09:23 initrd.img-2.6.21-2-686 -rw------- 1 root root 1235399 2007-08-06 09:18 initrd.img-2.6.22-1-686 -rw------- 1 root root 1324922 2007-09-08 01:39 initrd.img-2.6.22-2-686 -rw-r--r-- 1 root root 1260222 2007-06-01 08:56 vmlinuz-2.6.18-5-686 -rw-r--r-- 1 root root 1328272 2007-07-11 09:56 vmlinuz-2.6.21-2-686 -rw-r--r-- 1 root root 1359408 2007-07-29 20:51 vmlinuz-2.6.22-1-686 -rw-r--r-- 1 root root 1359760 2007-08-31 06:38 vmlinuz-2.6.22-2-686 I use yaird which makes very small initrds. initramfs-tools in 'dep' mode will get pretty close, but the default setting is 'most' which makes them 2-3 times bigger IIRC. You can also nicely see how the size is slowly increasing from one kernel version to another ... (though the kernel images seem to be pretty constant) Regards, Andrei -- If you can't explain it simply, you don't understand it well enough. (Albert Einstein)
Attachment:
signature.asc
Description: Digital signature