From: Harald Hoyer <harald-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: Hans de Goede <hdegoede-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Cc: initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: dracut and multiple iscsi/network disks
Date: Fri, 11 Jun 2010 12:40:18 +0200 [thread overview]
Message-ID: <4C121292.5030805@redhat.com> (raw)
In-Reply-To: <4C11D27C.3020807-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
On 06/11/2010 08:06 AM, Hans de Goede wrote:
> Hi,
>
> On 06/09/2010 05:47 PM, Harald Hoyer wrote:
>> http://dracut.git.sourceforge.net/git/gitweb.cgi?p=dracut/dracut;a=commitdiff;h=169f16715145fd087d61ef7fdfd7e9a3cbb68fc9
>>
>>
>>
>> adds support for multiple iscsi disks with the syntax:
>>
>> root=<normal block path or UUID or LABEL> \
>> netroot=iscsi:... netroot=iscsi:... netroot=iscsi:...
>>
>> which is suboptimal, because you can't specify it in the dhcp protocol.
>>
>> A better syntax would be a single netroot (also for FCoE disk) something
>> like:
>>
>> netroot=netdisks:iscsi:...[separator]iscsi:...[separator]fcoe:...
>>
>> What do you think? Any better ideas?
>>
>
> I think that will be a pain for the cmdline generating code in anaconda,
> one argument per disk please. Note having this as netroot syntax and
> a separate iscsi_disk= for the one argument per disk case would be fine.
>
> Regards,
>
> Hans
We could support both.. iscsi_disk= and the combined netroot=
prev parent reply other threads:[~2010-06-11 10:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-09 15:47 dracut and multiple iscsi/network disks Harald Hoyer
[not found] ` <4C0FB779.30005-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2010-06-10 7:06 ` Luca Berra
[not found] ` <20100610070647.GA23726-hdG+WfPrfN2JmafXlB/IVQ@public.gmane.org>
2010-06-10 8:19 ` Harald Hoyer
2010-06-11 6:06 ` Hans de Goede
[not found] ` <4C11D27C.3020807-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2010-06-11 10:40 ` Harald Hoyer [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4C121292.5030805@redhat.com \
--to=harald-h+wxahxf7alqt0dzr+alfa@public.gmane.org \
--cc=hdegoede-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.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.
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.