Pierre Neidhardt writes:
> Isn't there a more extensive log for "guix system reconfigure"?
You could look at the .scm files produced by "guix system reconfigure"
(the store paths should be printed to stdout). I'm afraid that, aside
from Shepherd's own messages, the console output is the
Hi Bengt,
Bengt Richter skribis:
> On +2019-08-29 14:41:51 +0200, Ludovic Courtès wrote:
>> Pierre Neidhardt skribis:
[...]
>> > Note that everything works alright. But I'm worried that this would
>> > fail on a new installation where the bootloader is missing :(
>>
>> Where the bootloader
On +2019-08-29 14:41:51 +0200, Ludovic Courtès wrote:
> Pierre Neidhardt skribis:
>
> > This is the last message in /var/log/messages:
> >
> > Aug 29 09:13:40 localhost shepherd[1]: Evaluating user expression (let*
> > ((services (map primitive-load (?))) # ?) ?).
> >
> >> Did
> >>
Ludovic Courtès writes:
> Where the bootloader is missing? The bootloader cannot be missing or
> the thing is not installed. :-)
No it's not missing, but I think the bootloader remained from the
previous working configs (before I configured the Btrfs file system).
Say I'd wipe the bootloader
Pierre Neidhardt skribis:
> This is the last message in /var/log/messages:
>
> Aug 29 09:13:40 localhost shepherd[1]: Evaluating user expression (let*
> ((services (map primitive-load (?))) # ?) ?).
>
>> Did
>> /var/log/messages or the console show anything?
>
> What console?
/dev/console, so
Hello,
Pierre Neidhardt skribis:
> After a guix pull on 0fc235a, guix system reconfigure stop at
>
> shepherd: Evaluating user expression (let* ((services (map primitive-load
> (?))) # ?) ?).
>
>
> instead of
>
> shepherd: Evaluating user expression (let* ((services (map primitive-load
>
