anchor.diff:          }
   
         // optionalAttrs cfg.server.enable
  -        { nfs_kernel_mountd =
  -          { name = "nfs-kernel-mountd";
  +        { mountd =
  +          { description = "Kernel NFS server - mount daemon";
   
  -            description = "Kernel NFS server - mount daemon";
  -
  -            startOn = "started nfs-kernel-nfsd";
  -            stopOn = "stopped nfs-kernel-statd";
  +            startOn = "started nfsd";
  +            stopOn = "stopped statd";
   
               daemonType = "fork";
   
  
positive.code:   rpc.mountd, rpc.nfsd
    rpc.statd, rpc.lockd (if necessary), and
    rpc.rquotad"
  
    I tried to mimic that with upstart, playing with stopping/stopped/started/starting
    events.
  
    I consider two scenarios:
      - Starting at boot. Then, portmap will emit a started event.
      - "restart nfs-kernel-exports". Then, portmap will not emit anything. Due
        to the comment in postStart, this will happen on nixos-rebuild if
        the exportfs file changed.
  
    From these scenarios, I came up with the startOn and stopOn at the time of commiting
    this comment.
  */
  
  
  
negative.code:   config =
    mkAssert
      (cfg.client.enable || cfg.server.enable -> config.services.portmap.enable) "
      Please enable portmap (services.portmap.enable) to use nfsd.
    " {
  
      services.portmap.enable = mkAlways (cfg.client.enable || cfg.server.enable);
  