<p><br>
On Mar 12, 2013 6:05 PM, "Harald Hoyer" <<a href="mailto:harald.hoyer@gmail.com">harald.hoyer@gmail.com</a>> wrote:<br>
><br>
> We have a big problem now with local-fs.target in the initrd-switch-root.target<br>
> now. Because local-fs.target is active now after serialization/deserialization,<br>
> the whole boot process after the switch-root is screwed. All units depending on<br>
> local-fs.target are started now immediately!!<br>
><br>
> Solutions I can think of is:<br>
> - not to serialize the targets as we do with the jobs now<br>
> - set all targets to TARGET_DEAD on switch_root</p>
<p>Hm, good catch. Sorry for not noticing this. Shouldn't this be a bug in isolate? If isolating a target causes a service to be started and the target is After the service, it seems intuitive that the target should be DEAD until the service is started?</p>
<p>Cheers,</p>
<p>Tom</p>