This is why I come to this:
I wanted to build up an initramfs for boot from nfs/aoe/iscsi, but not
determined from which of the three in time of making the initramfs. I found
it's
impossible with a BOOT set in the initramfs.conf. After looking at the scripts,
I came to the thought that BOOT should not be set in the initramfs.conf.
I have not used a Debian live, so don't know the live-initramfs affair. What I
know is about Ubuntu live CD, in which it set "BOOT=casper" in boot commandline
from the syslinux configure file. If there are some live-initramfs prefer to
set
BOOT in initramfs.conf rather than to set in syslinux configure file, I suggest
that the BOOT directive in initramfs be optional: it should not be a choice
from
"local | nfs" but an optional one for the live-initramfs.
From: maximilian attems
To: wol...@yahoo.com; 591...@bugs.debian.org
Sent: Sun, August 1, 2010 3:06:11 PM
Subject: Re: Bug#591025: Remove the irrelevent BOOT in initramfs.conf - patch
available
On Fri, 30 Jul 2010, wol...@yahoo.com wrote:
> Package: initramfs-tools
> Version: 0.97.2
>
> The BOOT switch should not be set in the initramfs.conf.
why do you come to that conclusion?
it is used by live-initramfs afair.
> It should be determined in boot time by the boot commandline, by
> either explicitly a "boot=foo" or implicitly such as "root=/root/nfs".
>
> I suggest that the BOOT directive in initramfs.conf be deprecated.
>
you don't give any rationale, so will close unless this gets motivated
properly and it be clear why we want that and what gain that would be.
