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