also sprach Russell Coker <[EMAIL PROTECTED]> [2007.01.08.2236 +0100]: > Where do I find this mdassemble? A grep of Contents-i386.gz gives: > usr/bin/mdassembler devel/monodoc-base
It's not yet packaged but part of the mdadm source package. > mdassemble would be good, but having it linked to busybox would be > better. Having dynamically linked binaries in the initramfs > causes a lot of disk space to be used by libc. Having two > statically linked binaries means two copies of common libc code > (EG printf). I am not entirely convinced that space gain warrants the risk of maintaining separate copies of critical code like RAID assembly. If a bug was found in mdadm's assembly, the fix would have to make it to busybox as well, which is extra coordination. This is not so much the case for the other tools busybox implements. I am not a huge fan of all-in-one solutions, and I see space not to be a concern really. If you have to watch out for every kilobyte, you're unlikely going to be using standard Debian kernels with initramfs anyway. And on a rescue CD or image, an extra megabyte likely doesn't hurt. -- Please do not send copies of list mail to me; I read the list! .''`. martin f. krafft <[EMAIL PROTECTED]> : :' : proud Debian developer, author, administrator, and user `. `'` http://people.debian.org/~madduck - http://debiansystem.info `- Debian - when you have better things to do than fixing systems "welcome to american airlines, sir. here's your avocado - remember to keep it turned on and with you at all times. please turn your luggage over to the armadillos for rootling." -- http://azure.humbug.org.au/~aj/armadillos.txt
signature.asc
Description: Digital signature (GPG/PGP)
