On 30/09/2013 08:24, pk wrote: > So what you're saying is that everything in /usr is system-critical? I > have gimp installed in /usr... I don't see a need to start gimp at boot > time. Maybe we should classify frozen-bubble as system-critical as well > (it's also in /usr)? > > Seriously, boot-critical would be something that the system cannot *boot > without*, which belongs in /. Everything else should be in /usr, i.e. > non-boot-critical. How hard is it to start *non-boot* (system) critical > *after* boot (things like sshd)? I do that today...
That is over-simplifying the problem and trivializing it. No-one ever said the *everythign* in /usr is criticial for boot. This is the problem: a. There exists code used at boot and early-user space time. It is critical that this code is available when needed. b. One cannot predict with absolute certainty 100% of the time what exactly that critical code is. c. many reasonable setups turn out to have such critical code in /usr, and this cannot be reliably predicted in advance Your second paragraph reveals that you beleive you already know everything you need to have to boot your system. Now do the same for every possible Gentoo user out there and have it work 100% of the time in ALL valid cases. Do you now see the problem and the fulls cope and impact of it? -- Alan McKinnon alan.mckin...@gmail.com
