Hi Carlo, Carlo Zancanaro <ca...@zancanaro.id.au> skribis:
> [ 18.924085] shepherd[1]: Service root-file-system has been started. > [ 18.932361] shepherd[1]: > [ 18.939972] shepherd[1]: Service user-file-systems has been started. > [ 18.947889] shepherd[1]: > [ 18.989611] shepherd[1]: waiting for udevd... > [ 19.001396] shepherd[1]: > [ 19.229174] udevd[267]: starting version 3.2.5 > failed to start service 'file-systems' > could not create '/dev/autofs': File exists > could not create '/dev/fuse': File exists > could not create '/dev/cuse': File exists > [ 19.525763] udevd[267]: starting eudev-3.2.5 [...] > [ 19.553794] udevd[267]: no sender credentials received, message ignored > failed to start service 'file-system-/dev/pts' [...] > [ 19.633995] udevd[267]: no sender credentials received, message ignored > failed to start service 'file-system-/dev/shm' [...] > [ 19.741025] udevd[267]: no sender credentials received, message ignored > failed to start service 'user-processes' > [ 19.773968] shepherd[1]: Service host-name has been started. > [ 19.784495] udevd[268]: starting version 3.2.5 > [ 19.797674] shepherd[1]: > could not create '/dev/autofs': File exists > could not create '/dev/fuse': File exists > [ 19.846310] udevd[269]: starting version 3.2.5 It looks as if udev failed to start initially, hence the subsequent “failed to start 'file-system-*'” messages, but then we appear to have several competing udevd processes, as if (exec-command (list udevd)) had been executed multiple times. Hmm not sure what’s going on… Ludo’.
