David Craven skribis:
>> Also, all the sysadmin work will happen in a bunch of Scheme files,
>> which means that everyone can now contribute to sysadmin, without
>> necessarily having shell access to the machines. No excuses! :-)
>
> Is there a reason why this isn't in gnu/system/examples?
It’
On Sun, Aug 21, 2016 at 7:38 PM, David Craven wrote:
> So guix doesn't work inside a vm - because /gnu/store is mounted
> readonly. To be able to offload arm builds once guix system vm
> --system=armhf-linux works, /gnu/store needs to be writeable.
>
> Can multiple daemons concurrently use the sam
So guix doesn't work inside a vm - because /gnu/store is mounted
readonly. To be able to offload arm builds once guix system vm
--system=armhf-linux works, /gnu/store needs to be writeable.
Can multiple daemons concurrently use the same store?
or alternatively, can we move the
(unless (zero? (sy
guix install probably needs support for handling local-file's. This is
what I added as a template to gnu/system/examples. Apart from easily
deploying build-machines, I think this is also useful for getting guix
build --system=armhf-linux working.
;; GuixSD configuration file for the build machines
> Also, all the sysadmin work will happen in a bunch of Scheme files,
> which means that everyone can now contribute to sysadmin, without
> necessarily having shell access to the machines. No excuses! :-)
Is there a reason why this isn't in gnu/system/examples? I think that
this is a common use
Hello!
After my talk yesterday at the GHM, Nacho and I talked a bit and Nacho
kindly offered to help make chapters.gnu.org the first build machine
that would use GuixSD.
So I quickly hacked up together, in guix-maintenance.git, a couple of
modules that allow us to give the high-level view of a bu
