On Tue, Jun 04, 2019 at 02:17:11PM +0200, pelzflorian (Florian Pelz) wrote: > On Tue, Jun 04, 2019 at 11:22:45AM +0200, Ludovic Courtès wrote: > > What’s the effect of this brokenness concretely? Is the wrong root file > > system mounted, or something like that? > > >
When removing quiet from the linux command line, shepherd complains incessantly that it is trying to load udev. All seems irrelevant, but: > I have multiple broken generation. On one that now for a third time > (on old generations without Ludo’s patches) led to a locked > /etc/shadow after booting I changed the line > (let ((pid (fork+exec-command (list udevd)))) > in gnu/services/base.scm to, I believe, this: > (let ((pid (fork+exec-command (list udevd "--debug-trace")))) > > (I am unsure if this is the same broken generation as on my first > report of the issue. I may have gotten confused.) > > This is unbootable, correct would have been --debug and not > --debug-trace. > The line in /gnu/store/kdql26k1pxgm74d94ryzk8fb4lg5q0ra-shepherd-udev.scm referenced from /gnu/store/b7mrb5pzsbbvhjmi8lbm9xa4wgvqbc7g-shepherd.conf referenced from the broken /var/guix/profiles/system-35-link/boot is (let ((pid (fork+exec-command (list udevd "--debug-trace" "--verbose")))) with an unneeded --verbose. > I may also have changed my syslog configuration to the incorrect > No, the syslog.conf in /gnu/store/y5nrfbj52vlnj77iyki9hbji8qjwk86d-syslog.conf referenced from /gnu/store/5bp6c0p357gaqikxkmvs0idrmvdrzf7h-shepherd-syslogd.scm referenced from /gnu/store/b7mrb5pzsbbvhjmi8lbm9xa4wgvqbc7g-shepherd.conf referenced from the broken /var/guix/profiles/system-35-link/boot appears to be the default syslog.conf. Booting this old generation and then an older working generation sometimes leads to a broken /etc/shadow. I do not yet know if a broken /etc/shadow can result when booting this old generation and then a new patched generation. I will reconfigure some more and try getting a bad /etc/shadow even with Ludo’s patches. Regards, Florian