Hello Léo,
> I get the same issue, the shepherd package uses GNU Guile 3.0.2 and GNU
> Guix provides GNU Guile 3.0.5 under the 'guile' package specification
> name.
>
> I am not sure this is the cause, since shepherd is wrapped to use GNU
> Guile 3.0.2.
>
> I am also still looking for a
Léo Le Bouter wrote:
> I get the same issue, the shepherd package uses GNU Guile 3.0.2 and GNU
> Guix provides GNU Guile 3.0.5 under the 'guile' package specification
> name.
>
> I am not sure this is the cause, since shepherd is wrapped to use GNU
> Guile 3.0.2.
>
> I am also still looking for
Hey Guix,
Reading https://guix.gnu.org/en/blog/2020/gnu-shepherd-user-services/, I was
inspired to start trying this out on my own. However, I immediately ran into
this huge mess:
$ shepherd
...
;;; WARNING: loading compiled file
Tobias Geerinckx-Rice wrote:
> This is about chrooting a serviceable Guix-the-package-manager,
> not running Guix System/Shepherd in the chroot, right?
Exactly. You've understood correctly.
> Did you manage to rescue your system in the end?
Yup!
> I find that claim surprising too.
Hey Guix,
Chatting on #guix, I heard that running Guix in a chroot was an "open problem."
Somehow, I seem to have stumbled into the right setup and managed to get it
working without any issues.
The channel asked me to write a blog post detailing what I did, so I'd like to
do it justice and first
Hello Guix,
I am hacking on the build scripts of an existing project and need to make sure
that my changes do not affect the actual build products.
Is there a good way to leverage guix for this?
Previously, I had been doing this manually by (deterministically) tarring up
the build products and
Chris Marusich wrote:
> I'm not sure. On your non-Guix setup, the crypttab exists in the
> initrd, right? And that initrd exists in the /boot directory on the
> external drive, right?
Yes. Specifically, I am using dracut to generate the initrd and I believe it is
the crypt module that copies
Nerd away!
It is indeed a nifty setup. Unfortunately, I can't point you at a manual, as
it's a self-baked solution. I actually ended up patching dracut to get the
whole thing working. Happily, upstream merged the patch, so in principle anyone
should be able to recreate my current setup.
Installing GuixSD for the first time. On a ThinkPad T400s, to boot!
Anyway, is there a straightforward way to configure a mapping device for LUKS
with a detached header? Otherwise, what's the best way to go about passing
command line options to the initrd cryptsetup call?
For a little context, I
