Hi, John Darrington <j...@gnu.org> skribis:
> Yet another patch. Here I check that the mount/umount succeeds by testing > that > /var/lib/nfs/pipefs is a member of the list returned by (mount-points). OK. > Regarding Ludo's suggestion to use a filesystem extention a la elogind - I > have > looked into that possibility, but so far as I can see using a service > extension > does not allow a "provision" field, so I don't know how to make the other > services > dependent upon it. Also I don't see from the elogind example how to specify > an > alternative mount point and then to pass that mount point to dependent > services. > (I cannot imagine why anyone would want to do that, but hey - guix is > supposed to > be hackable!) I'd be happy to change it later if someone can explain how to > do it. Yes, let’s keep it for later. For future reference, as I wrote in <https://lists.gnu.org/archive/html/guix-devel/2016-09/msg01096.html>, the Shepherd service corresponding to the file system object would be called ‘file-system-/var/lib/nfs/pipefs’. This is the name you would write in ‘requirement’. > > > > > * gnu/services/nfs.scm (pipefs-service-type): New Variable, > (gss-service-type): New Variable, (idmap-service-type) New Variable. > > * doc/guix.texi (Network File system): New Node. No need to capitalize “node” and “variable.” OK with this patch, thank you! Ludo’.
