<html><head></head><body> -- Sent from my Android phone with K-9 Mail. Please excuse my brevity. <div class="gmail_quote">"Manuel Amador (Rudd-O)" <rudd-o@rudd-o.com> wrote:<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"> I want systemd to mount file systems in parallel. That is all. ZFS does not use fstab for the purpose, it has its own zfs mount -a command. ZFS mount -a will fail when: / zfs /home ext4 /home/rudd-o zfs As it will attempt to mount /home/rudd-o without /home mounted. It will also not mount fs'es in parallel. Systemd has none of those problems. Without systemd mointing ZFS file systems, also, there is no way to mount zfs file systems early. Wich means no /var or /usr on zfs.! Mounting zfs filesystems through systemd fixes that. So how do i tell systemd that we have just discovered a new filesystem to be mounted then? Hotplug hook? -- Sent from my Android phone with K-9 Mail. Please excuse my brevity. <div class="gmail_quote">Kay Sievers <kay.sievers@vrfy.org> wrote:<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"> <pre style="white-space: pre-wrap; word-wrap:break-word; font-family: sans-serif">On Fri, Nov 4, 2011 at 13:22, Manuel Amador <rudd-o@rudd-o.com> wrote: > I am developing systemd support for ZFS: > as you can see, I create the units early on bootup using a generator (a > mechanism that is entirely undocumented, tsk). It isn't documented, because it's use is not encouraged for most use cases. The main focus is to be able to support compatibility wrappers for sysv init scripts, fstab, cryptab, means: read a legacy file and create a systemd unit from it. It is not a hotplug hook. > Now, this will happen during udev settle. What I want is to generate more > units when pools are discovered and their file systems require to be mounted > automatically. That is, I need to re-run the generator and generate new > units, and then tell systemd to daemon-reload. The generator runs _before_ systemd starts, if you need to reload systemd's config during bootup, generators are absolutely not what you are looking for. I did not look at the details, maybe you want an instantiated foo@.service? I fear, that you are trying to force the systemd service engine into a storage management daemon, which is not what we want. If instantiated services don't help, a more general/higher level description of the problem might be helpful for us to understand the problem. Kay </pre></blockquote></div></blockquote></div></body></html>