unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Jason Self <jason@bluehome.net>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH] Kernel Configuration
Date: Thu, 25 Sep 2014 18:00:17 +0200	[thread overview]
Message-ID: <87lhp7her2.fsf@gnu.org> (raw)
In-Reply-To: <1411600434.23396@bluehome.net> (Jason Self's message of "Wed, 24 Sep 2014 16:13:56 -0700 (PDT)")

"Jason Self" <jason@bluehome.net> skribis:

> Ludovic Courtès said:
>> Furthermore I would rather keep CONFIG_VIRTIO_BLK=m rather than =y
>> precisely because that module only makes sense when running a QEMU
>> guest and not otherwise.
>> 
>> WDYT?
>
> My reason for making it y instead of m is:
>
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/902951
>
> I don't use it myself, but think EC2. My understanding is that
> ramdisk-less boot is a popular thing because it speeds up booting and
> makes maintenance easier. Ideally it'd be easy to set up Guix anywhere.

RAM disks are a pain that results from Linux’s lack of support for the
multiboot spec, if you ask me.  ;-)  It’s a reduced pain in Guix because
there’s an easy, automated way to build initrds.

I’m fine with switching to CONFIG_VIRTIO_BLK=y, but then references to
that module in vm.scm or linux-initrd.scm code must be removed, with a
comment saying that this is expected to be compiled in.

Thanks,
Ludo’.

      reply	other threads:[~2014-09-25 16:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-24 20:53 [PATCH] Kernel Configuration Jason Self
2014-09-24 22:05 ` Ludovic Courtès
2014-09-24 23:13   ` Jason Self
2014-09-25 16:00     ` Ludovic Courtès [this message]

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=87lhp7her2.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=guix-devel@gnu.org \
    --cc=jason@bluehome.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 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).