From: Jan Nieuwenhuizen <janneke@gnu.org>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 41541@debbugs.gnu.org
Subject: [bug#41541] [PATCH 8/8] system: Add `hurd-activation'.
Date: Sat, 06 Jun 2020 16:21:51 +0200 [thread overview]
Message-ID: <871rms2s1s.fsf@gnu.org> (raw)
In-Reply-To: <87o8pwv4ht.fsf@gnu.org> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\=22'\?\= \=\?utf-8\?Q\?s\?\= message of "Sat, 06 Jun 2020 13:05:34 +0200")
Ludovic Courtès writes:
> "Jan (janneke) Nieuwenhuizen" <janneke@gnu.org> skribis:
>
>> +(define (hurd-activation-script gexps)
>> + (activate-current-system #:kernel-command-line command-line)
>
> It seems that ‘command-line’ is unbound here, no?
I don't think so...activation will be loaded from RC (following commit),
which is a guile script started by RUNSYSTEM:
--8<---------------cut here---------------start------------->8---
...
exec ${system}/rc \"$@\"
--8<---------------cut here---------------end--------------->8---
> I was wondering: if the only thing that differs between Linux and Mach
> is the command line, could we keep the same activation script for both
> cases, and instead move the conditional to (gnu build activation), like:
>
(if (string-contains %host-type "linux-gnu")
linux-command-line
mach-command-line)
> Does that make sense?
Yes, much better now. Using (command-line), though.
This used to be much more complicated, when stuff didn't cross build
correctly etc.
Greetings,
Janneke
--
Jan Nieuwenhuizen <janneke@gnu.org> | GNU LilyPond http://lilypond.org
Freelance IT http://JoyofSource.com | Avatar® http://AvatarAcademy.com
next prev parent reply other threads:[~2020-06-06 14:23 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20200604135914.4499-1-janneke@gnu.org>
[not found] ` <20200604135914.4499-2-janneke@gnu.org>
2020-06-06 10:45 ` [bug#41541] [PATCH 1/8] system: Add 'hurd' field to <operating-system> Ludovic Courtès
2020-06-06 11:14 ` Jan Nieuwenhuizen
[not found] ` <20200604135914.4499-3-janneke@gnu.org>
2020-06-06 10:48 ` [bug#41541] [PATCH 2/8] bootloader: Extend `<menu-entry>' for multiboot Ludovic Courtès
2020-06-06 12:00 ` Jan Nieuwenhuizen
[not found] ` <20200604135914.4499-4-janneke@gnu.org>
[not found] ` <87eeqsmyxy.fsf@gnu.org>
2020-06-06 10:55 ` [bug#41541] [PATCH 3/8] system: Add 'multiboot-modules' field to <boot-parameters> Ludovic Courtès
2020-06-07 7:39 ` Jan Nieuwenhuizen
[not found] ` <20200604135914.4499-5-janneke@gnu.org>
2020-06-06 10:57 ` [bug#41541] [PATCH 4/8] bootloader: grub: Add support for multiboot Ludovic Courtès
2020-06-06 12:08 ` Jan Nieuwenhuizen
[not found] ` <20200604135914.4499-6-janneke@gnu.org>
2020-06-06 10:57 ` [bug#41541] [PATCH 5/8] system: Use 'hurd' package in label Ludovic Courtès
[not found] ` <20200604135914.4499-7-janneke@gnu.org>
[not found] ` <875zc4mxtu.fsf@gnu.org>
2020-06-06 10:58 ` [bug#41541] [PATCH 6/8] system: examples: Add bare-hurd.tmpl Jan Nieuwenhuizen
2020-06-06 16:49 ` Mathieu Othacehe
2020-06-06 22:44 ` Jan Nieuwenhuizen
2020-06-06 10:59 ` Ludovic Courtès
2020-06-06 12:34 ` Jan Nieuwenhuizen
[not found] ` <20200604135914.4499-9-janneke@gnu.org>
2020-06-06 11:05 ` [bug#41541] [PATCH 8/8] system: Add `hurd-activation' Ludovic Courtès
2020-06-06 14:21 ` Jan Nieuwenhuizen [this message]
[not found] ` <20200604135914.4499-8-janneke@gnu.org>
2020-06-06 11:08 ` [bug#41541] [PATCH 7/8] services: hurd: Add `hurd-etc-service' Ludovic Courtès
2020-06-06 14:31 ` Jan Nieuwenhuizen
2020-06-07 20:02 ` Ludovic Courtès
2020-06-07 20:31 ` Jan Nieuwenhuizen
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=871rms2s1s.fsf@gnu.org \
--to=janneke@gnu.org \
--cc=41541@debbugs.gnu.org \
--cc=ludo@gnu.org \
/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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).