Grub Development Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Vladimir 'φ-coder/phcoder' Serbinenko" <phcoder@gmail.com>
To: The development of GNU GRUB <grub-devel@gnu.org>
Subject: Re: Grub overview/tutorial available
Date: Sat, 17 Apr 2010 17:39:49 +0200	[thread overview]
Message-ID: <4BC9D645.7000008@gmail.com> (raw)
In-Reply-To: <1271482788.16191.4.camel@simon-laptop>

[-- Attachment #1: Type: text/plain, Size: 1912 bytes --]

Simon Kitching wrote:
> Hi All,
>
> Just FYI, I've written up what I've learned about Grub during the last
> few weeks and put it up here:
>
> http://people.apache.org/~skitching/MineOfInformation/linux/Booting_Linux_on_x86_with_Grub2.html
>
> This is more detailed than simple "user level", but doesn't get into any
> code details. More at the "advanced sysadmin" level perhaps.
>
> Any feedback/corrections welcome; I'm fairly new to Grub so probably
> have some mistakes in there.
>   
"This tool(grub-emu) can be used to install Grub." <--- wrong (outdated)
" Note also that there are a few commands that can be run in the “grub
shell” that are not available in a real Grub environment (because they
would be pointless)," <--- likewise
insmod /boot/grub/normal.mod normal <-- only one of 2 arguments and it
won't set prefix resulting in further problems. Correct action is:

set prefix=(<disk>)/boot/grub
insmod normal
normal

'Grub “legacy” (the 0.x series) could only boot kernels that support the
“multiboot” specification.' <--- grub legacy has a linux loader too
'As Grub2 boots kernels by invoking a helper module (“linux”, “xnu”,
“bsd”), it can boot any kernel for which the appropriate helper module
has been written. Of course if a kernel supports multiboot, then writing
such a helper module is much simpler!'
Modules are NOT ''helpers'. They are separate loaders. and multiboot
needs no 'helpers'

    linux $root/mykernel root=xyz ---->  linux ($root)/mykernel root=xyz

' search –set=MYDEV – search.label mylabel MYDEV' at very least actually
try the commands you supply

> Regards,
> Simon
>
>
>
>
> _______________________________________________
> Grub-devel mailing list
> Grub-devel@gnu.org
> http://lists.gnu.org/mailman/listinfo/grub-devel
>
>   


-- 
Regards
Vladimir 'φ-coder/phcoder' Serbinenko



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 293 bytes --]

  parent reply	other threads:[~2010-04-17 15:40 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-17  5:39 Grub overview/tutorial available Simon Kitching
2010-04-17  6:31 ` Seth Goldberg
2010-04-17  6:31 ` J. Bakshi
2010-04-17 15:39 ` Vladimir 'φ-coder/phcoder' Serbinenko [this message]
2010-04-17 21:20   ` Simon Kitching
2010-04-17 21:24     ` Vladimir 'φ-coder/phcoder' Serbinenko

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=4BC9D645.7000008@gmail.com \
    --to=phcoder@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox