mountall.conf file. I need to have it wait for a custom filesystem module, which is getting modprobed via module-init-tools.conf; however, both these conf files appear to have the same prereq of 'start on startup' 
<kreign> is there any way to make one a prereq of the other? 
<kreign> from looking at the files it looks like I can do an "emits fs_module" and then have mountall.conf with "start on (startup and started fs_module)" - is this correct?
<JanC> "emits" is documentation
<JanC> so it does nothing on its own
<kreign> JanC, ok; how can I specify that basic chain of events?
<kreign> JanC, start on (startup and started init-module-tools) ?
<kreign> er module-init-tools
<JanC> sounds like that might work
<kreign> JanC, or am I going about this the wrong way?
<kreign> i'm assuming it's not whitespace sensitive...
<JanC> I guess the "startup" part can be left out too
<kreign> hmm probably.
<JanC> and maybe you can make the modprobe for that specific module its own task, so that mountall can start earlier?
<kreign> JanC, hmm I don't think mountall will be able to start earlier - module-init-tools is the direct prerequisite. 
<JanC> also depends on whether boot time is important  ;)
<kreign> not so much.
 * kreign misses the old way of doing things, somewhat.
<kreign> JanC, I'd think that any filesystem modules should be loaded before filesystems try to mount, anyway.
<JanC> normally they will be loaded automatically?
<kreign> JanC, that does not seem to be the case, in this regard.
<kreign> JanC, the modules aren't strictly "linux compliant" per se
<kreign> (ok, not going to lie - it's zfs, and I"ve also got to import the zpool in the module-init-tools.conf)
<JanC> kreign: I think for most filesystems, their mount utility loads the modules, or something like that
<JanC> I guess 'mount.zfs' (or whatever it's called) doesn't?
<kreign> JanC, running mountall manually once in does the trick (with 'auto' as an fstab option)
<kreign> JanC, it just looks like mountall is running prior to zfs module getting loaded (define