Gentoo Archives: gentoo-user

From: Michael Mol <mikemol@×××××.com>
To: gentoo-user@l.g.o
Subject: Re: [gentoo-user] Re: Anyone switched to eudev yet?
Date: Thu, 27 Dec 2012 20:09:04
Message-Id: CA+czFiCwBFGtmxntuW_Y+Rg=q0jmvDdjFDJrwQJb+Bzqd3PzFg@mail.gmail.com
In Reply to: Re: [gentoo-user] Re: Anyone switched to eudev yet? by Volker Armin Hemmann
1 On Thu, Dec 27, 2012 at 2:43 PM, Volker Armin Hemmann
2 <volkerarmin@××××××××××.com> wrote:
3 >
4 > Am Sonntag, 23. Dezember 2012, 19:44:43 schrieb Nuno J. Silva:
5 > > On 2012-12-23, Alan Mackenzie wrote:
6 > > > On Sun, Dec 23, 2012 at 07:03:25PM +0200, Nuno J. Silva wrote:
7 > > >> On 2012-12-23, Alan McKinnon wrote:
8 > > >> > On Sun, 23 Dec 2012 12:22:24 +0200
9 > > >> >
10 > > >> > nunojsilva@×××××××.pt (Nuno J. Silva) wrote:
11 > > >> >> On 2012-12-18, Alan McKinnon wrote:
12 > > >> >> > On Tue, 18 Dec 2012 09:08:53 -0500
13 > > >> >> > Michael Mol <mikemol@×××××.com> wrote:
14 > > >> >> >
15 > > >> >> > This sentence summarizes my understanding of your post nicely:
16 > > >> >> >> Now, why is /usr special? It's because it contains executable code
17 > > >> >> >> the system might require while launching.
18 > > >> >> >
19 > > >> >> > Now there are only two approaches that could solve that problem:
20 > > >> >> >
21 > > >> >> > 1. Avoid it entirely
22 > > >> >> > 2. Deal with it using any of a variety of bootstrap techniques
23 > > >> >> >
24 > > >> >> > #1 is handled by policy, whereby any code the system might require
25 > > >> >> > while launching is not in /usr.
26 > > >> >> >
27 > > >> >> > #2 already has a solution, it's called an init*. Other solutions
28 > > >> >> > exist but none are as elegant as a throwaway temporary filesystem
29 > > >> >> > in RAM.
30 > > >> >>
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 > > >>
36 > > >> Then I suppose you can surely explain in a nutshell why can't init
37 > > >> scripts simply do that?
38 > > >
39 > > > Because certain people with influence have rearranged the filesystem so
40 > > > that programs within /usr are absolutely necessary for booting; they are
41 > > > needed _before_ init has a chance to mount /usr. So either /usr has to
42 > > > be in the root partition, or crazy kludges need to be used to mount /usr
43 > > > before the kernel runs init.
44 > >
45 > > I surely don't know the udev architecture well enough, but if this is
46 > > all done by the udev daemon, can't we just "mount /usr" before the
47 > > daemon is started? The only needed things should be mount (which is
48 > > under /bin here) and /etc/fstab.
49 > >
50 >
51 > and a device node in /dev - like /dev/sda2. And how do you get that one
52 > without udev?
53 >
54 > oops?
55
56
57 Yeah, the "oops" is on the part of the udev team, which decided to put
58 a critical piece of software there. Which is the origin of this whole
59 uproar for the past year or so.
60
61 --
62 :wq