1 |
On Sun, Dec 23, 2012 at 07:03:25PM +0200, Nuno J. Silva wrote: |
2 |
> On 2012-12-23, Alan McKinnon wrote: |
3 |
|
4 |
> > On Sun, 23 Dec 2012 12:22:24 +0200 |
5 |
> > nunojsilva@×××××××.pt (Nuno J. Silva) wrote: |
6 |
|
7 |
> >> On 2012-12-18, Alan McKinnon wrote: |
8 |
|
9 |
> >> > On Tue, 18 Dec 2012 09:08:53 -0500 |
10 |
> >> > Michael Mol <mikemol@×××××.com> wrote: |
11 |
|
12 |
|
13 |
> >> > This sentence summarizes my understanding of your post nicely: |
14 |
|
15 |
> >> >> Now, why is /usr special? It's because it contains executable code |
16 |
> >> >> the system might require while launching. |
17 |
|
18 |
> >> > Now there are only two approaches that could solve that problem: |
19 |
|
20 |
> >> > 1. Avoid it entirely |
21 |
> >> > 2. Deal with it using any of a variety of bootstrap techniques |
22 |
|
23 |
> >> > #1 is handled by policy, whereby any code the system might require |
24 |
> >> > while launching is not in /usr. |
25 |
|
26 |
> >> > #2 already has a solution, it's called an init*. Other solutions |
27 |
> >> > exist but none are as elegant as a throwaway temporary filesystem |
28 |
> >> > in RAM. |
29 |
|
30 |
> >> What about just mounting /usr as soon as the system boots? |
31 |
|
32 |
|
33 |
> > Please read the thread next time. The topic under discussion is |
34 |
> > solutions to the problem of not being able to do exactly that. |
35 |
|
36 |
> Then I suppose you can surely explain in a nutshell why can't init |
37 |
> scripts simply do that? |
38 |
|
39 |
Because certain people with influence have rearranged the filesystem so |
40 |
that programs within /usr are absolutely necessary for booting; they are |
41 |
needed _before_ init has a chance to mount /usr. So either /usr has to |
42 |
be in the root partition, or crazy kludges need to be used to mount /usr |
43 |
before the kernel runs init. |
44 |
|
45 |
> -- |
46 |
> Nuno Silva (aka njsg) |
47 |
> http://njsg.sdf-eu.org/ |
48 |
|
49 |
-- |
50 |
Alan Mackenzie (Nuremberg, Germany). |