1 |
vivo75@×××××.com wrote: |
2 |
> First problem udev/SD has is that it can't see all the file system labels, |
3 |
> for some reason it only see sda and sdb so it's able to partly proceed in |
4 |
> the boot sequence, mount / (root) but can't mount anything else. |
5 |
|
6 |
What software parses the filesystem labels when you boot with openrc? |
7 |
|
8 |
(I ask because I never use labels myself.) |
9 |
|
10 |
|
11 |
> a) SD does not re-calculate it's deptree/services when exiting from rescue |
12 |
> shell, it still try to start the "virtual" services as fstab would have |
13 |
> never modified, a reboot is needed |
14 |
|
15 |
systemctl --system daemon-reload ? |
16 |
|
17 |
|
18 |
> b) since it does not work even after reboot, there must be something else, |
19 |
> but what? this bring us to the point |
20 |
|
21 |
I'm not contesting that there is a problem with your systemd setup, |
22 |
and maybe it is a problem with systemd, but unless you know for sure |
23 |
maybe it's premature to say that "it" is systemd? I would investigate |
24 |
what the problem really is. |
25 |
|
26 |
|
27 |
> SD has mainly two things to debug boot `systemctl dump` and |
28 |
> `systemd-journal` |
29 |
|
30 |
Hm, debug boot like how? I mean: what problem did you want to resolve |
31 |
when you say that you were debugging boot? |
32 |
|
33 |
|
34 |
> impossible even to understand WHAT failed to start, not to mention WHY |
35 |
|
36 |
There are no logfiles for the individual services? |
37 |
|
38 |
|
39 |
> the magnificient binary log^W^W journal is kept on tmpfs (in ram) so |
40 |
> it's not even available at boot in different situation. |
41 |
|
42 |
I'm not sure what the purpose of the binary log is, maybe it makes |
43 |
sense to have it per session, but in any case I guess the services |
44 |
should be doing some logging of their own? |
45 |
|
46 |
|
47 |
> every try needed many minutes because SD wait for a long timeout before |
48 |
> going to the rescue shell |
49 |
|
50 |
I would be interested in understanding why there was a long wait, I |
51 |
mean: what was systemd waiting for? |
52 |
|
53 |
|
54 |
> - SD does not see anything else than systemd for boot. |
55 |
> Interaction with SD from a livecd, is difficult, almost all tools don't |
56 |
> work because SD is not running. |
57 |
|
58 |
I just work with the files on disk. The only time I use tools is if |
59 |
systemd is running and needs to get told about updates. I don't think |
60 |
there are any files that are not plain text, so I don't think any |
61 |
tools are actually required. |
62 |
|
63 |
|
64 |
> transported on remote server administration this is a *nightmare* |
65 |
|
66 |
If there's a way to boot into a shell prompt, even if it is just bash |
67 |
running as pid 1, then any system can be fixed. It requires knowing a |
68 |
lot about how the system works though, so a lot about systemd if the |
69 |
system uses systemd. Ie. knowing what files to change how in order to |
70 |
accomplish desired results. |
71 |
|
72 |
|
73 |
> various provider offer livecd like system which don't offer SD. |
74 |
> so no easy migration, no easy first install, every failure is |
75 |
> definitive, a no go |
76 |
|
77 |
I don't understand this at all. Even if we go with what you write, |
78 |
then I expect that some providers will start to offer an ecosystem of |
79 |
systemd-optimized experiences for those who want it - but I do not |
80 |
believe for a second that those would somehow be exclusive to other |
81 |
systems. |
82 |
|
83 |
|
84 |
> - the journal will never become simpler, can only grow, debugging things in |
85 |
> the shell will be nearly impossible for excess of data (and lack of useful |
86 |
> one if it continue this way) |
87 |
|
88 |
Configure it to write into files? |
89 |
|
90 |
|
91 |
> - virtual/autogenerated services are and will be difficult to cope with, |
92 |
> impossible to disable |
93 |
|
94 |
Hm, do they matter? |
95 |
|
96 |
|
97 |
> - every change in the early boot procedure will require reboot |
98 |
|
99 |
Is that different from another pid 1? |
100 |
|
101 |
|
102 |
> - which sum to: SD will work until it work, when something does not will be |
103 |
> a royal pain to solve _and_ nothing else other than SD will be available to |
104 |
> alleviate the pain |
105 |
|
106 |
This does not match my experience at all. I don't know what you did |
107 |
wrong though, your email wasn't very specific. :\ |
108 |
|
109 |
|
110 |
//Peter |