[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [PATCH] Kernel Configuration
From: |
Ludovic Courtès |
Subject: |
Re: [PATCH] Kernel Configuration |
Date: |
Thu, 25 Sep 2014 18:00:17 +0200 |
User-agent: |
Gnus/5.130011 (Ma Gnus v0.11) Emacs/24.3 (gnu/linux) |
"Jason Self" <address@hidden> 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’.