Hi, Maxim Cournoyer <maxim.courno...@gmail.com> writes:
> Hi, > > Fredrik Salomonsson <platt...@posteo.net> writes: > > [...] > >> ---✂---------------------------------------------------------------------------- >> … >> shepherd: Evaluating user expression (and (defined? (quote transient?)) (map >> (# ?) ?)). >> guix system: warning: exception caught while executing 'start' on service >> 'file-system-/media/Valhalla': >> In procedure mount: mount "fafner:/srv/nfs4/Valhalla" on >> "///media/Valhalla": Invalid argument >> guix system: warning: some services could not be upgraded >> … >> -------------------------------------------------------------------------------- >> >> So that's probably what's happening during boot. >> >> I have no idea how it transforms the mount-point from "/media/Valhalla" >> to "///media/Valhalla" and if that's a red herring. >> >> Any ideas what I'm doing wrong? > > Nothing; mounting an NFS file system at boot is not supported currently > with Guix System; see the related issue #47706. Ah, ok. Thanks for the info. > My current ugly workaround is to define the mount points with "(mount? > #f)" and mount them via a script post boot, e.g.: > > --8<---------------cut here---------------start------------->8--- > (file-system > (device "jami-buildmachine-04:/srv/nfs/jami") > (mount-point "/var/cache/jami") > (create-mount-point? #t) > (type "nfs") > (mount? #f) > (options "soft,user")) > --8<---------------cut here---------------end--------------->8--- Yeah, I think I'll just add a shepherd service to my home configuration that mounts and unmounts my NFS device until this is resolved. -- s/Fred[re]+i[ck]+/Fredrik/g
