All of lore.kernel.org
 help / color / mirror / Atom feed
From: sky knight <sky_knight02@yahoo.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: Grub memory usages help
Date: Mon, 29 Dec 2008 11:05:13 -0800 (PST)	[thread overview]
Message-ID: <784841.14744.qm@web90307.mail.mud.yahoo.com> (raw)

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


From: Colin D Bennett <colin@gibibit.com>
Subject: Re: Grub memory usages help
To: "The development of GRUB 2" <grub-devel@gnu.org>
Cc: sky_knight02@yahoo.com
Date: Monday, December 29, 2008, 12:57 PM

On Mon, 29 Dec 2008 09:38:05 -0800 (PST)
sky knight <sky_knight02@yahoo.com> wrote:

Memory usage details?  Can you elaborate?  Do you mean "how to allocate
memory on the heap", or how to determine the amount of memory used by
GRUB at runtime?

As for how to create a graphical menu theme:

Example themes
  Screenshots: <http://grub.gibibit.com/Themes>;
  Theme source archive:
    <http://grub.gibibit.com/files/grub-themes-src-2008-08-15.tgz>.

Theme file format is documentation
  <http://grub.gibibit.com/Theme_format>,
  <http://grub.enbug.org/ThemeFormat>.

More information about the graphical menu system for developers
  <http://grub.gibibit.com/gfxmenu_design>,
  <http://grub.enbug.org/Subprojects/GraphicalMenu>.

In order to use graphical menu themes, you currently need to build from
a snapshot of my branch, which contains the gfxmenu feature.  It is in
the process of being merged into GRUB mainline, but it's not there
yet.  Here's the info on building it:


Building GRUB+gfxmenu, 19 December 2008
=======================================

I have posted a source tarball
(<http://grub.gibibit.com/files/cdbmain_r867.tar.bz2>) to make it easy
to build GRUB 2 with gfxmenu support on your own if you want to install
it on a real machine instead of just testing with the premade ISO image
that I created.

To build and install GRUB 2, the following commands should suffice::

   tar -xjf cdbmain_r867.tar.bz2
   cd cdbmain_r867
   mkdir build
   cd build
   sh ../configure --prefix=YOUR_PREFIX_DIR
   make
   make install  (or sudo make install, depending on the prefix)

Some people have tried to extract the files from the premade gfxmenu
demo ISO I provide on the download page, and either insert new files
into the ISO image or install the files to a hard drive device.  This
usually does not work, so I recommend building GRUB 2 with gfxmenu from
the source tarball yourself if you want to boot your machine with it or
customize it.
Thanks that sure gave me lots of input for GRUB GFX.I want to know both about the how to allocate
memory on the heap & how to determine the amount of memory used by
GRUB at runtime.-Welkin-


      

[-- Attachment #2: Type: text/html, Size: 3585 bytes --]

             reply	other threads:[~2008-12-29 19:05 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-29 19:05 sky knight [this message]
  -- strict thread matches above, loose matches on Subject: below --
2008-12-29 17:38 Grub memory usages help sky knight
2008-12-29 18:57 ` Colin D Bennett

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=784841.14744.qm@web90307.mail.mud.yahoo.com \
    --to=sky_knight02@yahoo.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.