1 |
Hi Devs, |
2 |
|
3 |
Not sure if you are aware of the discussions on the gentoo-user list about the |
4 |
upcoming change where systemd and udev require /usr to be available prior to |
5 |
starting of udev. |
6 |
|
7 |
I would like to know what the position of the Gentoo developers is with |
8 |
regarding this and how best to deal with this. |
9 |
|
10 |
There have been several use-cases mentioned in the other list describing the |
11 |
need for a seperate /usr and /var partition. I also have these on seperate |
12 |
partitions. |
13 |
|
14 |
The use for an initrd/initramfs/... will create an additional layer of |
15 |
complexity a lot of us users are not really waiting for, especially as we are |
16 |
not seeing any issues with our current systems. |
17 |
It's also one extra thing that can go wrong and it is not clear how we could |
18 |
solve the situation where we messed something up with the initramfs and can't |
19 |
get to the tools in single-usermode to try and fix it. That is if we can even |
20 |
get access to the machine in question. |
21 |
|
22 |
I have raised a possible alternative on the other list and would like to know |
23 |
how you, the Developers, feel about it. |
24 |
|
25 |
My idea is, to me at least, simple. |
26 |
"udev" is split into 2 parts: |
27 |
1) "udevd", which creates the /dev-tree based on the events it currently gets |
28 |
2) "actiond" processes all the actions "udevd" puts in a seperate queue. |
29 |
|
30 |
I think that if "udevd" is started at boot-time and "actiond" only after |
31 |
"localmount" has finished, there shouldn't be the situation where a script in |
32 |
the udev-configuration fails because of missing files. |
33 |
Even if it does, then this can be handled in "actiond" itself and placed in a |
34 |
retry-queue. |
35 |
|
36 |
With a smaller udev, the chances of it failing should also be less. (less |
37 |
code-lines to check) and as long as the /dev-entries are created, these can be |
38 |
used to manually mount the other partitions to get to the point where the |
39 |
system can be fixed to get it back to a workable state. |
40 |
|
41 |
If, in the currently planned form, udev fails, it will be necessary to use a |
42 |
rescue-cd/usb to boot the system, try to fix it inside a chroot where it's not |
43 |
easy to check what is actually going wrong during the boot-process as the |
44 |
different tools can then not be run with the error-messages printed to the |
45 |
console. |
46 |
|
47 |
Kind regards, |
48 |
|
49 |
Joost Roeleveld |