On Fri, 2010-07-16 at 12:11 +0200, Giacomo A. Catenazzi wrote: > Also the booting system is a changing area > We moved from sysv style to inserv, Isn't that still sysv + just some auto-"ordering" and so? > IMHO requiring that at call of /bin/init (the first program > called in the new root filesystem at boot) that the "essential > debian system" is ready it is IMHO very impractical for > many setups. Don't get me wrong,... (in what I've written before)... I did not meant to request that everything essential must go into something that is guaranteed available in the root-fs. As some of you already pointed out this wouldn't make sense for e.g. *dpkg*... and also not for all binaries from coreutils (e.g. dircolors). But I think: 1) the policy description of essential should be clarified then, as now it really reads "be available and usable on the system at all times". I guess we should at least exclude initramfs from that,... an perhaps also all or parts of the boot process. Why do I think this is important? Well,... one thing the policy implies on essential packages is, that you don't have to depend on them (in terms of package dependencies).... I guess its logical to conclude that one also doesn't have to check for the core stuff like cp/cat/rm... this would really clutter many scripts. But right now one may think that _all_ coreutils packages are guaranteed to be always there. 2) Personally, I'd prefer to put some of the current /usr/bin utilities from coreutils to /bin, especially [, test, printf ... but actually some more... I guess this makes /bin not much larger, but would be a nice benefit. Cheers, Chris.
Attachment:
smime.p7s
Description: S/MIME cryptographic signature