From: jbranso@dismail.de
To: "Tobias Geerinckx-Rice" <me@tobias.gr>,
"Mitchell Schmeisser" <mitchellschmeisser@librem.one>
Cc: "Peter Polidoro" <peter@polidoro.io>,
"Csepp" <raingloom@riseup.net>,
guix-devel@gnu.org
Subject: Re: Oniro or Guix on Zephyr kernel?
Date: Sat, 25 Feb 2023 17:06:26 +0000 [thread overview]
Message-ID: <8ee692272e09a5a293b9aacb97e22c8a@dismail.de> (raw)
In-Reply-To: <5072eb912433c1376a5b8bd223513b77@tobias.gr>
February 24, 2023 2:35 PM, "Tobias Geerinckx-Rice" <me@tobias.gr> wrote:
> Hi,
>
> On 2023-02-24 19:36, Mitchell Schmeisser wrote:
>
>> I don't think the guix daemon is technically > required
>> for the shepherd to boot (being the daemon is a shepherd process
>> itself).
>
> No, not at all. I think this is a common (and not unreasonable!) assumption we Guixers forget
> exists.
>
> The ‘Guix daemon’ is not required to run Guix software or Guix System, only for store operations
> (building, GC'ing, …).
>
> The name ‘guix-build-daemon’ would have been closer to the truth.
Thanks for clarifying. So, guix system requires a shepherd daemon to be running correct?
That shepherd daemon starts at boot and runs as PID 1 and starts all system services.
Does the guix-build-daemon start lazily or only when needed? So if I booted up my guix system laptop, and only browsed
the internet, never typed in any "guix " command, would the guix-build-daemon ever run?
>
> Kind regards,
>
> T G-R
>
> Sent from a Web browser. Excuse or enjoy my brevity.
next prev parent reply other threads:[~2023-02-25 17:07 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-23 14:42 Oniro or Guix on Zephyr kernel? Peter Polidoro
2023-02-23 21:43 ` Csepp
2023-02-24 12:43 ` Joshua Branson
2023-02-24 15:19 ` Peter Polidoro
2023-02-24 16:52 ` jbranso
2023-02-24 18:36 ` Mitchell Schmeisser via Development of GNU Guix and the GNU System distribution.
2023-02-24 19:35 ` Tobias Geerinckx-Rice
2023-02-24 19:43 ` Felix Lechner via Development of GNU Guix and the GNU System distribution.
2023-02-25 13:45 ` Peter Polidoro
2023-02-25 14:15 ` Mitchell Schmeisser via Development of GNU Guix and the GNU System distribution.
2023-02-25 14:16 ` Mitchell Schmeisser via Development of GNU Guix and the GNU System distribution.
2023-02-25 15:19 ` Peter Polidoro
2023-02-25 15:27 ` Mitchell Schmeisser via Development of GNU Guix and the GNU System distribution.
2023-03-01 21:55 ` Mitchell Schmeisser via Development of GNU Guix and the GNU System distribution.
2023-02-25 17:06 ` jbranso [this message]
2023-02-27 19:10 ` Efraim Flashner
2023-03-01 8:45 ` Ryan Sundberg
2023-03-04 17:26 ` Joshua Branson
2023-03-05 0:42 ` Ryan Sundberg
2023-02-25 18:15 ` Ludovic Courtès
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8ee692272e09a5a293b9aacb97e22c8a@dismail.de \
--to=jbranso@dismail.de \
--cc=guix-devel@gnu.org \
--cc=me@tobias.gr \
--cc=mitchellschmeisser@librem.one \
--cc=peter@polidoro.io \
--cc=raingloom@riseup.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.