From: Bruce Dubbs <bruce.dubbs@gmail.com>
To: The development of GNU GRUB <grub-devel@gnu.org>
Subject: Re: The submenu command shows a text-based menu when using a GFX theme.
Date: Sun, 26 Feb 2012 10:50:10 -0600 [thread overview]
Message-ID: <4F4A62C2.9070500@gmail.com> (raw)
In-Reply-To: <1330273259.58740.YahooMailNeo@web113512.mail.gq1.yahoo.com>
Towheed Mohammed wrote:
> I have tested this on separate distros, including but not limited to:
> ArchLinux, Debian (and Debian-based distros), Slackware, Fedora,
> VectorLinux and openSUSE (some others I can't recall ATM), all with
> and without separate /boot partitions and all with GRUB 1.99
> installed.. Actually, my demo theme is located in /usr/share/grub
> and not in /boot/grub. As it is, the fully qualified filename works
> as intended. Placing the themes in /usr/share/grub removes the
> incompatibility of having a separate /boot partition and also removes
> any incompatibility from some distro that use /boot/grub2 instead of
> /boot/grub.
>
> If the unreliability is because of separate /boot partitions and/or
> other distros using /boot/grub2 instead of /boot/grub then please
> consider placing themes in /usr/share/grub instead of /boot/grub.
> This removes the unreliability and ensures the theme will display
> properly across all distros and all partitioning schemes.
>
> I don't think users should place files in /boot/grub. Files there
> should only be those necessary for the bootloader to function
> properly. Although it's a protected directory, it's all to easy for
> 'inexperienced' users to simply 'su' and delete critical files
> (unintentionally while working on themes) thus preventing their
> system from booting.
>
> Please keep this feature and consider placing themes in
> /usr/share/grub.
This is not a good suggestion. I have several instances of /usr/share
on my system in different root filesystem partitions. Which one would
grub use? All the files for the boot process need to be in a single
partition.
/boot/grub2 is a distro specific issue and distros that use it need to
maintain it.
-- Bruce
next prev parent reply other threads:[~2012-02-26 16:50 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-23 1:50 The submenu command shows a text-based menu when using a GFX theme Towheed Mohammed
2012-02-23 5:24 ` Vladimir 'φ-coder/phcoder' Serbinenko
2012-02-24 1:24 ` Towheed Mohammed
2012-02-24 7:44 ` Vladimir 'φ-coder/phcoder' Serbinenko
2012-02-24 22:50 ` Towheed Mohammed
2012-02-24 23:03 ` Vladimir 'φ-coder/phcoder' Serbinenko
2012-02-26 2:18 ` Towheed Mohammed
2012-02-26 9:27 ` Vladimir 'φ-coder/phcoder' Serbinenko
2012-02-26 16:20 ` Towheed Mohammed
2012-02-26 16:50 ` Bruce Dubbs [this message]
2012-02-26 17:02 ` Vladimir 'φ-coder/phcoder' Serbinenko
2012-02-26 17:31 ` Towheed Mohammed
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=4F4A62C2.9070500@gmail.com \
--to=bruce.dubbs@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 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.