On Tue, 18 Dec 2012 09:08:53 -0500 Michael Mol <mike...@gmail.com> wrote:
This sentence summarizes my understanding of your post nicely: > Now, why is /usr special? It's because it contains executable code the > system might require while launching. Now there are only two approaches that could solve that problem: 1. Avoid it entirely 2. Deal with it using any of a variety of bootstrap techniques #1 is handled by policy, whereby any code the system might require while launching is not in /usr. #2 already has a solution, it's called an init*. Other solutions exist but none are as elegant as a throwaway temporary filesystem in RAM. I should be clear that I do not necessarily support Lennart's solutions, but I do support his perception of the problem (at least partially). We cannot support situations where *launch* code is haphazardly scattered in location X and this must always work for all values of X. We already have a remarkably parallel situation in /boot - in order to boot at all, the code running at that point in time needs to be able to find stuff, and it finds it (by policy) in what we will later call /boot. I see this /usr debate as the same thing on a larger scale. -- Alan McKinnon alan.mckin...@gmail.com
