On Fri, 01.03.13 15:33, Harald Hoyer (har...@redhat.com) wrote: > > Am 01.03.2013 15:30, schrieb Lennart Poettering: > > On Fri, 01.03.13 15:13, har...@redhat.com (har...@redhat.com) wrote: > > > >> From: Harald Hoyer <har...@redhat.com> > >> > >> Write out "JobTimeoutSec=0" for the device the mountpoint (which does > >> not timeout) waits for. > >> > >> This helps with grabbing a cup of coffee while booting and not have > >> the crypto password dialog timeout and systemd in a failed state. > > > > Hmm, this hooks into "wait", which is initialized from the kernel > > cmdline rootwait? What are the precise semantics of the kernel there > > regarding this flag, in a non-initrd case? We probably should mimic the > > kernel here is good as we can... > > > > So, in the non-initrd case: what does rootwait do on the kernel cmdline? > > And what happens if it is not used? > > rootwait [KNL] Wait (indefinitely) for root device to show up. > Useful for devices that are detected asynchronously > (e.g. USB and MMC devices).
Yeah, that's what I read, too, but I cannot make sense of it. See above: what is different from when it is not used? Or to be precise: what does the kernel precisely do when rootwait is *not* passed? Lennart -- Lennart Poettering - Red Hat, Inc. _______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel