mkinitrd unification across distributions
 help / color / mirror / Atom feed
From: Hannes Reinecke <hare-l3A5Bk7waGM@public.gmane.org>
To: Harald Hoyer <harald-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Cc: initramfs <initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: iBFT oddities
Date: Wed, 04 Jun 2014 09:52:34 +0200	[thread overview]
Message-ID: <538ED042.8000904@suse.de> (raw)

Hi all,

I'm trying to setup a machine with root on iSCSI via iBFT
(on SR-IOV, yay!).

But anyhow, I'll be setting 'ip=ibft' on the commandline as per 
documentation and the iBFT settings are applied and everything is 
nice and dandy.

It's only that dracut complains during boot:

Jun 03 16:28:11 localhost dracut-cmdline[80]: ibft
Jun 03 16:28:11 localhost dracut-cmdline[80]: Warning: Please supply 
bootdev argument for multiple ip= lines
Jun 03 16:28:11 localhost dracut-cmdline[80]: Warning: Setting 
bootdev to 'ibft0'

Looking closer, setting 'ip=ibft' triggers 'ibft_to_cmdline()',
which will add _another_ ip= argument to the dracut commandline.
And consequently parse_ip_opts() complains here.

While it's quite easy to fix (just ignore ip=ibft when checking for 
duplicate ip arguments), I do wonder whether this is the correct way.

Thing is, 'ip=ibft' is not really an ip setting, but rather a marker 
that iBFT should be evaluated.
As such, wouldn't 'rd.iscsi.firmware=ibft' be a more appropriate 
setting?
Seeing that the ip argument is added to the commandline anyway, 
having a duplicate 'ip=ibft' setting does look a bit odd.
And confuses the logic ...

Cheers,

Hannes
-- 
Dr. Hannes Reinecke		      zSeries & Storage
hare-l3A5Bk7waGM@public.gmane.org			      +49 911 74053 688
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg
GF: J. Hawn, J. Guild, F. Imendörffer, HRB 16746 (AG Nürnberg)

             reply	other threads:[~2014-06-04  7:52 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-04  7:52 Hannes Reinecke [this message]
     [not found] ` <538ED042.8000904-l3A5Bk7waGM@public.gmane.org>
2014-06-04 11:50   ` iBFT oddities Harald Hoyer
     [not found]     ` <538F0800.80008-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2014-06-04 12:10       ` Hannes Reinecke
     [not found]         ` <538F0CAD.5050407-l3A5Bk7waGM@public.gmane.org>
2014-06-04 12:16           ` Harald Hoyer

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=538ED042.8000904@suse.de \
    --to=hare-l3a5bk7wagm@public.gmane.org \
    --cc=harald-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox