Comment 22 for bug 434232

>So, isn't it a solution to simply make root filesystem depend on
>cryptsetup in cases where interactive input is needed? I.e. when no
>other (xsplash, key file) method is used?

Actually, root filesystem already depends on cryptsetup by design when root partition is encrypted, since it will never get mounted until cryptsetup prompt gets the good passphrase (therefore upstart wait in that situation). In other situations, it's not possible to make filesystem "depends" on cryptsetup since filesystem is a event, not a task. This bug only concern cryptsetup installations which does not mount root filesystem AFAIK.

>What if any of the essential directories (/var, /home, ...) reside on
>other filesystems, are mounted onto the root filesystem, like when
>encrypted or on a remote server and might not be available yet?

That is a very interesting question, I wouldn't be able to answer that (I'm not a developer myself). My guess is that everything except / is ignored since many other mount point can be necessary or not for the system, depending on the distribution and many other variables (ex. : /var, /media/*) . I guess that there is many chances that it's not upstart job to look at all these mount points and decide which ones are really needed since there are many many possibilities, unless upstart follows some FHS specification, but I might be wrong. I don't know how upstart handle these cases, but I think that it only react to the event of / becoming mounted and readable/writable.