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