From: Bean <bean123@126.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: Command extension suggestions
Date: Thu, 14 Jun 2007 18:24:19 +0800 [thread overview]
Message-ID: <20070614102419.GA633@ws3.vdp.com> (raw)
In-Reply-To: <871wgex473.fsf@xs4all.nl>
On Thu, Jun 14, 2007 at 11:42:24AM +0200, Marco Gerards wrote:
> Bean <bean123@126.com> writes:
>
> [...]
>
> >> That sounds much cleaner IMHO. But IIRC (md) is already in use by the
> >> RAID/LVM stuff ?
> >>
> >
> > Maybe (mem) ?
>
> When would this be useful?
You can use it to dump physical memory, for example,
od (mem)+2
dump first 1K of memory
od --skip-bytes=0x413 --read-bytes=2 (mem)
dump the word at 0x413.
I can't think of other use at the moment.
>
> > Also, I don't know if GRUB2 kernel support initrd. You can start grub4dos
> > like this:
> >
> > kernel /grub.exe
> > initrd /aa.img
> >
> > Inside grub4dos, the initrd can be access using (rd). It would be nice if
> > grub2 support this kind of usage.
>
> You can use the loopback command to do this, if you want to access a
> filesystem image.
>
> loopback (loop) /foo/bar.img
> ls -l (loop)/
>
Initrd can still be useful. In some case, it's not easy to access the boot
media, such as, cdrom or pxe. To boot from such media, you can either put
everything in core.img, or you can create a minimum core.img, and put other
files, like *.mod, grub.cfg, font, etc, in an initrd. The initrd can be
loaded along with core.img, using loader such as isolinux or pxelinux.
--
Bean <bean123@126.com>
next prev parent reply other threads:[~2007-06-14 10:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-14 3:46 Command extension suggestions Bean
2007-06-14 6:08 ` Robert Millan
2007-06-14 6:24 ` Bean
2007-06-14 9:42 ` Marco Gerards
2007-06-14 10:24 ` Bean [this message]
2007-06-14 10:49 ` Marco Gerards
2007-06-14 11:31 ` Bean
2007-06-14 11:50 ` Marco Gerards
2007-06-14 13:08 ` Bean
2007-06-14 13:48 ` Marco Gerards
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=20070614102419.GA633@ws3.vdp.com \
--to=bean123@126.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.