[email protected] skribis: > +(define (hurd-loopback-shepherd-service _) > + "Return the 'loopback' Shepherd service." > + > + (list (shepherd-service > + (documentation "Dummy for bootstrapping (gnu services) on the > Hurd.") > + (provision '(loopback)) > + (requirement '()) > + (start #~(const #t)) > + (stop #~(const #t)) > + (respawn? #f)))) > + > +(define hurd-loopback-service-type > + (service-type > + (name 'loopback) > + (extensions (list (service-extension shepherd-root-service-type > + hurd-loopback-shepherd-service))) > + (compose concatenate) > + (extend first-of-two) > + (default-value '(loopback)) ;canary for hurd-service->shepherd-service > + (description "Dummy service to bootstrap (gnu services) on the > +Hurd.")))
I believe the code currently used in ‘static-networking-service’ to setup the loopback device on GNU/Linux should also work on GNU/Hurd: it uses the “traditional” ioctls provided by (guix build syscalls). So hopefully we don’t need a Hurd-specific variant. Ludo’.
