| 1 |
On 2012-12-18, Alan McKinnon wrote: |
| 2 |
|
| 3 |
> On Tue, 18 Dec 2012 09:08:53 -0500 |
| 4 |
> Michael Mol <mikemol@×××××.com> wrote: |
| 5 |
> |
| 6 |
> |
| 7 |
> This sentence summarizes my understanding of your post nicely: |
| 8 |
> |
| 9 |
>> Now, why is /usr special? It's because it contains executable code the |
| 10 |
>> system might require while launching. |
| 11 |
> |
| 12 |
> Now there are only two approaches that could solve that problem: |
| 13 |
> |
| 14 |
> 1. Avoid it entirely |
| 15 |
> 2. Deal with it using any of a variety of bootstrap techniques |
| 16 |
> |
| 17 |
> #1 is handled by policy, whereby any code the system might require |
| 18 |
> while launching is not in /usr. |
| 19 |
> |
| 20 |
> #2 already has a solution, it's called an init*. Other solutions exist |
| 21 |
> but none are as elegant as a throwaway temporary filesystem in RAM. |
| 22 |
|
| 23 |
What about just mounting /usr as soon as the system boots? |
| 24 |
|
| 25 |
<snip/> |
| 26 |
|
| 27 |
-- |
| 28 |
Nuno Silva (aka njsg) |
| 29 |
http://njsg.sdf-eu.org/ |
Archives