Alan McKinnon wrote: > On Sun, 23 Dec 2012 19:03:25 +0200 > nunojsi...@ist.utl.pt (Nuno J. Silva) wrote: > >> On 2012-12-23, Alan McKinnon wrote: >> >>> On Sun, 23 Dec 2012 12:22:24 +0200 >>> nunojsi...@ist.utl.pt (Nuno J. Silva) wrote: >>> >>>> On 2012-12-18, Alan McKinnon wrote: >>>> >>>>> On Tue, 18 Dec 2012 09:08:53 -0500 >>>>> Michael Mol <mike...@gmail.com> wrote: >>>>> >>>>> >>>>> This sentence summarizes my understanding of your post nicely: >>>>> >>>>>> Now, why is /usr special? It's because it contains executable >>>>>> code the system might require while launching. >>>>> Now there are only two approaches that could solve that problem: >>>>> >>>>> 1. Avoid it entirely >>>>> 2. Deal with it using any of a variety of bootstrap techniques >>>>> >>>>> #1 is handled by policy, whereby any code the system might >>>>> require while launching is not in /usr. >>>>> >>>>> #2 already has a solution, it's called an init*. Other solutions >>>>> exist but none are as elegant as a throwaway temporary filesystem >>>>> in RAM. >>>> What about just mounting /usr as soon as the system boots? >>> >>> Please read the thread next time. The topic under discussion is >>> solutions to the problem of not being able to do exactly that. >> Then I suppose you can surely explain in a nutshell why can't init >> scripts simply do that? >> > It is trivially easy to create a circular loop whereby code required to > mount /usr now resides on /usr. > > Which is the entire thrust of this whole thread. >
When I reboot, I get a lot of errors about /var being empty, since it is not mounted yet. It appears it wants /var as well as /usr early on in the boot process. It boots regardless of the errors tho. For the record Nuno, I have / and /boot on regular partitions. I have everything else, /home, /usr, /var and /usr/portage on LVM partitions. Until recently, I NEVER needed a init thingy and had zero errors while booting. Once this 'needing /usr on /' started a few months ago, I was told I would need one to boot. The claim being it was broken all the time but odd that it worked for the last 9 years with no problem, might add, I only been using Linux for the last 9 years but it also would have worked before that. So, Nuno, everything was fine until they started moving things to a place where it shouldn't be. Now, we have people working on eudev which will replace udev and allow us to boot with a separate /usr and no init thingy either. Basically, putting it back like it was, for many years I might add. Dale :-) :-) -- I am only responsible for what I said ... Not for what you understood or how you interpreted my words!
