1 |
On Sun, 23 Dec 2012 12:22:24 +0200 |
2 |
nunojsilva@×××××××.pt (Nuno J. Silva) wrote: |
3 |
|
4 |
> On 2012-12-18, Alan McKinnon wrote: |
5 |
> |
6 |
> > On Tue, 18 Dec 2012 09:08:53 -0500 |
7 |
> > Michael Mol <mikemol@×××××.com> wrote: |
8 |
> > |
9 |
> > |
10 |
> > This sentence summarizes my understanding of your post nicely: |
11 |
> > |
12 |
> >> Now, why is /usr special? It's because it contains executable code |
13 |
> >> the system might require while launching. |
14 |
> > |
15 |
> > Now there are only two approaches that could solve that problem: |
16 |
> > |
17 |
> > 1. Avoid it entirely |
18 |
> > 2. Deal with it using any of a variety of bootstrap techniques |
19 |
> > |
20 |
> > #1 is handled by policy, whereby any code the system might require |
21 |
> > while launching is not in /usr. |
22 |
> > |
23 |
> > #2 already has a solution, it's called an init*. Other solutions |
24 |
> > exist but none are as elegant as a throwaway temporary filesystem |
25 |
> > in RAM. |
26 |
> |
27 |
> What about just mounting /usr as soon as the system boots? |
28 |
|
29 |
|
30 |
Please read the thread next time. The topic under discussion is |
31 |
solutions to the problem of not being able to do exactly that. |
32 |
|
33 |
|
34 |
-- |
35 |
Alan McKinnon |
36 |
alan.mckinnon@×××××.com |