Ricardo Wurmus writes:
> The issue here is likely that operating-system-services returns all
> services, including those that are added by the operating system
> machinery.
Yes. I ran into this myself the other day.
The solution seems to be to use "operating-system-user-services" in
place of "op
raingloom writes:
> I have an operating-system called bingobongo. I have another called
> greg that inherits the bingobongo config. If I leave the services field
> empty in greg, there is no issue. If I define it as
> (operating-system-services bingobongo) then all hell breaks loose and I
> get
raingloom writes:
> I have an operating-system called bingobongo. I have another called
> greg that inherits the bingobongo config. If I leave the services field
> empty in greg, there is no issue. If I define it as
> (operating-system-services bingobongo) then all hell breaks loose and I
> get t
I have an operating-system called bingobongo. I have another called
greg that inherits the bingobongo config. If I leave the services field
empty in greg, there is no issue. If I define it as
(operating-system-services bingobongo) then all hell breaks loose and I
get the aforementioned error and no
