all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: guix-devel@gnu.org
Subject: Re: [PATCH] linux-initrd: Introduce way to add more packages to initrd.
Date: Tue, 02 Aug 2016 14:53:58 +0200	[thread overview]
Message-ID: <871t27wcux.fsf@gnu.org> (raw)
In-Reply-To: <20160801182636.GG1062@venom> ("Tomáš Čech"'s message of "Mon, 1 Aug 2016 20:26:36 +0200")

Hello,

Tomáš Čech <sleep_walker@gnu.org> skribis:

> On Mon, Aug 01, 2016 at 06:09:12PM +0200, Ludovic Courtès wrote:
>>Hello,
>>
>>Tomáš Čech <sleep_walker@gnu.org> skribis:
>>
>>> Ping after week - is there interest in this patch?
>>
>>I didn’t comment on the patch specifically because I thought my reply
>>might make you change your mind.  ;-)
>>
>>  https://lists.gnu.org/archive/html/guix-devel/2016-07/msg01241.html
>
> Thanks for that, I'm still trying to digest that bite. I'm sorry for
> being a bit slow on Guile.

No problem.  Since you pinged, I thought you had digested it.  ;-)

>>All the packages used by the initrd are automatically part of the
>>initrd.  The proposed patch would allow people to add unused packages to
>>the initrd.
>
> It is for the packages which you may want to use interactivelly in
> case of failure or for some extra initrd hacking you may not want/be
> able to write in Guile.
>
> Features like
> - extra authentication
> - full disk encryption
> - root on NFS
> - LVM :)
> - ...

OK but if you need these packages, for instance because you have a LUKS
boot device, they’ll already be in the initrd.  No need to manually list
them in #:extra-packages.

>>Could you explain how/when this would be used?  Maybe as commands for
>>use by Bournish when it’s used as a rescue shell?
>
> I agree that it is more for debugging and to balance my inability to
> express it in Guile but it lowers the barrier a bit.
>
> Bournish is too young to rely on it. I miss pipes, accessing files in
> different directories or `ls' with wildcards. I can put in minimal
> static busybox which is more than sufficient for rescue, problem
> analysis or even data recovery.
>
> I like the idea of Bournish but I'd rather have an alternative
> until it is more capable.

I agree, but hopefully, you don’t run into Bournish too often?

I guess my main concern (again, as a lazy maintainer) is the cost of
turning ‘base-initrd’ into a kitchen sink, as discussed in the other
thread about #:extra-modules.

I would prefer to provide simple tools that people can build upon, like
‘expression->initrd’ or the ‘raw-initrd’ procedure I proposed, than
trying to come up with a one-size-fits-all procedure with many
parameters.

WDYT?

Thanks,
Ludo’.

  reply	other threads:[~2016-08-02 12:54 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-25  7:46 extending initrd Tomáš Čech
2016-07-25 20:10 ` [PATCH] linux-initrd: Introduce way to add more packages to initrd Tomáš Čech
2016-08-01 10:39   ` Tomáš Čech
2016-08-01 15:44     ` Andy Wingo
2016-08-02  7:43       ` extra-packages - second wave Tomáš Čech
2016-08-02  7:43         ` [PATCH 1/2] linux-initrd: Introduce way to add more packages to initrd Tomáš Čech
2016-08-02  7:43         ` [PATCH 2/2] doc: Document extra-packages argument of base-initrd Tomáš Čech
2016-08-02  8:19           ` Vincent Legoll
2016-08-01 16:09     ` [PATCH] linux-initrd: Introduce way to add more packages to initrd Ludovic Courtès
2016-08-01 18:26       ` Tomáš Čech
2016-08-02 12:53         ` Ludovic Courtès [this message]
2016-08-02 18:03           ` Tomáš Čech
2016-07-25 21:48 ` extending initrd 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=871t27wcux.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=guix-devel@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 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.