All of lore.kernel.org
 help / color / mirror / Atom feed
From: Robert Millan <rmh@aybabtu.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: [PATCH] Use extcmd to handle bsd arguments.
Date: Sun, 23 Aug 2009 12:53:30 +0200	[thread overview]
Message-ID: <20090823105330.GI4130@thorin> (raw)
In-Reply-To: <d7ead6de0908220522i504ae08bwd8248f8522ae3c70@mail.gmail.com>

On Sat, Aug 22, 2009 at 02:22:24PM +0200, Vladimir 'phcoder' Serbinenko wrote:
> Hello. Currently bsd loaders inspects argv[1] for boot options but the
> treat argv[1] as if it always was prefixed by dash ('-') and
> completely ignores options in argv[n], n>1. This leads to unexpected
> results like
> freebsd /kernel verbose
> is parsed like verbose ('v'), dfltroot ('r') and single ('s')
> freebsd /kernel -v -s
> is parsed only like verbose and not verbose and single.
> Additionally help shows no information about these options. This patch
> delegates option parsing to lib/arg.c and so achieves good option
> passing, GNU-style options support and provides help. Unfortunately
> booting with some options has no noticeable effect so I couldn't
> document what they do

Please go ahead (I assume you've tested it on the 3 *BSD kernels).

Btw, you capitalized two of the "Load kernel of ..." messages but not the
NetBSD one:

> +  cmd_freebsd = grub_register_extcmd ("freebsd", grub_cmd_freebsd,
> +				      GRUB_COMMAND_FLAG_BOTH,
> +				      "freebsd FILE", "Load kernel of FreeBSD.",
> +				      freebsd_opts);
> +  cmd_openbsd = grub_register_extcmd ("openbsd", grub_cmd_openbsd,
> +				      GRUB_COMMAND_FLAG_BOTH,
> +				      "openbsd FILE", "Load kernel of OpenBSD.",
> +				      openbsd_opts);
> +  cmd_netbsd = grub_register_extcmd ("netbsd", grub_cmd_netbsd,
> +				     GRUB_COMMAND_FLAG_BOTH,
> +				     "netbsd FILE", "load kernel of NetBSD",
> +				     netbsd_opts);

-- 
Robert Millan

  The DRM opt-in fallacy: "Your data belongs to us. We will decide when (and
  how) you may access your data; but nobody's threatening your freedom: we
  still allow you to remove your data and not access it at all."



      reply	other threads:[~2009-08-23 10:53 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-22 12:22 [PATCH] Use extcmd to handle bsd arguments Vladimir 'phcoder' Serbinenko
2009-08-23 10:53 ` Robert Millan [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=20090823105330.GI4130@thorin \
    --to=rmh@aybabtu.com \
    --cc=grub-devel@gnu.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.