All of lore.kernel.org
 help / color / mirror / Atom feed
From: Florian Kirstein <xenlist@custom.ray.net>
To: xen-devel@lists.xensource.com
Cc: Ian Campbell <Ian.Campbell@XenSource.com>
Subject: Re: [PATCH] fix: growing kernel commandline
Date: Fri, 19 Jan 2007 12:59:31 +0100	[thread overview]
Message-ID: <20070119125931.A829@web.ray.net> (raw)
In-Reply-To: <1169202558.6453.16.camel@localhost.localdomain>; from Ian.Campbell@XenSource.com on Fri, Jan 19, 2007 at 10:29:18AM +0000

Hi,

> I'm actually just about to push a straight backport of the fix which
> went into unstable. If further fixes are required on top of that we
> should consider making them in xen-unstable first.
I agree for anything further than what I've done. But the switching of
ip= and root= parameter in the processing, basically just an exchange of
the two blocks:

arg_ip = sxp.child_value(image_sxp, 'ip')
if arg_ip and not re.search(r'ip=[^ ]+', kernel_args):
   kernel_args = 'ip=%s ' % arg_ip + kernel_args

and:

arg_root = sxp.child_value(image_sxp, 'root')
if arg_root and not re.search(r'root=', kernel_args):
   kernel_args = 'root=%s ' % arg_root + kernel_args

seems to be riskless, if you do this additional to the -unstable patch
we should be on the safe side, I hope :) Otherwise ip= and root= parameter
will change their order on the commandline (because they now prepend
instead of append themselves), and I thought keeping that intact for
bad parsers was the main reason for all of this... That's why I did
this change when backporting the fix.

(:ul8er, r@y

  reply	other threads:[~2007-01-19 11:59 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-17 22:36 Two problems with DomU reboot (cmdline, duplicate domains) Florian Kirstein
2007-01-19  9:41 ` [PATCH] fix: growing kernel commandline Florian Kirstein
2007-01-19 10:29   ` Ian Campbell
2007-01-19 11:59     ` Florian Kirstein [this message]
2007-01-21  8:59 ` Bug: Problematic DomU Duplication on reboot Florian Kirstein

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=20070119125931.A829@web.ray.net \
    --to=xenlist@custom.ray.net \
    --cc=Ian.Campbell@XenSource.com \
    --cc=xen-devel@lists.xensource.com \
    /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.