All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Grégoire Sutre" <gregoire.sutre@labri.fr>
To: The development of GNU GRUB <grub-devel@gnu.org>
Subject: Re: Invalid symbol table on NetBSD boot
Date: Sat, 09 Jan 2010 16:33:42 +0100	[thread overview]
Message-ID: <4B48A1D6.8030401@labri.fr> (raw)
In-Reply-To: <20100108213537.GA22519@thorin>

Robert Millan wrote:

>> grub> multiboot /netbsd.generic -z root=wd0a
> 
> There was an intentional backward-incompatible (but still compatible with
> the specification) change.  The equivalent command on GRUB 2 would be:
> 
> grub> multiboot /netbsd.generic /netbsd.generic -z root=wd0a

Ok.

> First argument is the file being open;  in GRUB Legacy it's implicitly also
> the first arg passed to payload, which is less flexible than letting user
> specify it.  It doesn't have to be the filename at all, and usually the
> payload doesn't need this information.

I don't know how it is used in NetBSD, the only difference I could 
observe is the sysctl parameter `machdep.booted_kernel' which is set to 
the file name of the booted kernel (or empty if the information could 
not be derived from the multiboot command-line).

> I'm not sure if this explains your missing word problem, but it sounds like
> it could be related.

Yes, it sure explains the problem, thanks!  I had a look at the 
multiboot command-line parsing in the NetBSD kernel: the first argument 
in the command-line is ignored (here `-z') as it is assumed to be the 
kernel file name.

Anyway, the above solution (duplicating the kernel file name) is simple 
enough. :-)

Grégoire



      reply	other threads:[~2010-01-09 15:33 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-06 18:07 Invalid symbol table on NetBSD boot Grégoire Sutre
2010-01-07 21:36 ` Robert Millan
2010-01-08  0:44   ` Grégoire Sutre
2010-01-08 21:35     ` Robert Millan
2010-01-09 15:33       ` Grégoire Sutre [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=4B48A1D6.8030401@labri.fr \
    --to=gregoire.sutre@labri.fr \
    --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.