| 1 |
Alan McKinnon wrote: |
| 2 |
> On Sun, 23 Dec 2012 19:03:25 +0200 |
| 3 |
> nunojsilva@×××××××.pt (Nuno J. Silva) wrote: |
| 4 |
> |
| 5 |
>> On 2012-12-23, Alan McKinnon wrote: |
| 6 |
>> |
| 7 |
>>> On Sun, 23 Dec 2012 12:22:24 +0200 |
| 8 |
>>> nunojsilva@×××××××.pt (Nuno J. Silva) wrote: |
| 9 |
>>> |
| 10 |
>>>> On 2012-12-18, Alan McKinnon wrote: |
| 11 |
>>>> |
| 12 |
>>>>> On Tue, 18 Dec 2012 09:08:53 -0500 |
| 13 |
>>>>> Michael Mol <mikemol@×××××.com> wrote: |
| 14 |
>>>>> |
| 15 |
>>>>> |
| 16 |
>>>>> This sentence summarizes my understanding of your post nicely: |
| 17 |
>>>>> |
| 18 |
>>>>>> Now, why is /usr special? It's because it contains executable |
| 19 |
>>>>>> code the system might require while launching. |
| 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 |
>>>> What about just mounting /usr as soon as the system boots? |
| 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 |
>> Then I suppose you can surely explain in a nutshell why can't init |
| 36 |
>> scripts simply do that? |
| 37 |
>> |
| 38 |
> It is trivially easy to create a circular loop whereby code required to |
| 39 |
> mount /usr now resides on /usr. |
| 40 |
> |
| 41 |
> Which is the entire thrust of this whole thread. |
| 42 |
> |
| 43 |
|
| 44 |
When I reboot, I get a lot of errors about /var being empty, since it is |
| 45 |
not mounted yet. It appears it wants /var as well as /usr early on in |
| 46 |
the boot process. It boots regardless of the errors tho. |
| 47 |
|
| 48 |
For the record Nuno, I have / and /boot on regular partitions. I have |
| 49 |
everything else, /home, /usr, /var and /usr/portage on LVM partitions. |
| 50 |
Until recently, I NEVER needed a init thingy and had zero errors while |
| 51 |
booting. Once this 'needing /usr on /' started a few months ago, I was |
| 52 |
told I would need one to boot. The claim being it was broken all the |
| 53 |
time but odd that it worked for the last 9 years with no problem, might |
| 54 |
add, I only been using Linux for the last 9 years but it also would have |
| 55 |
worked before that. |
| 56 |
|
| 57 |
So, Nuno, everything was fine until they started moving things to a |
| 58 |
place where it shouldn't be. Now, we have people working on eudev which |
| 59 |
will replace udev and allow us to boot with a separate /usr and no init |
| 60 |
thingy either. Basically, putting it back like it was, for many years I |
| 61 |
might add. |
| 62 |
|
| 63 |
Dale |
| 64 |
|
| 65 |
:-) :-) |
| 66 |
|
| 67 |
-- |
| 68 |
I am only responsible for what I said ... Not for what you understood or how you interpreted my words! |
Archives