grub-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: The submenu command shows a text-based menu when using a GFX theme.


From: Towheed Mohammed
Subject: Re: The submenu command shows a text-based menu when using a GFX theme.
Date: Sun, 26 Feb 2012 08:20:59 -0800 (PST)

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.

Thanks.

Towheed Mohammed


----- Original Message -----
From: Vladimir 'φ-coder/phcoder' Serbinenko <address@hidden>
To: address@hidden
Cc: 
Sent: Sunday, February 26, 2012 5:27 AM
Subject: Re: The submenu command shows a text-based menu when using a GFX theme.

On 26.02.2012 03:18, Towheed Mohammed wrote:
> Also consider this.  As in the case of the image component, it's file 
> property allows for a fully qualified filename:
> + image {
>    file = "/usr/share/grub/themes/demo/images/gnu.jpg"
This possibility is kept for backward compatibility but shouldn't be used in 
new themes and is unreliable. Consider e.g. a case of separate /boot. Perhaps 
we should remove this possibility altogether.

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


_______________________________________________
Grub-devel mailing list
address@hidden
https://lists.gnu.org/mailman/listinfo/grub-devel




reply via email to

[Prev in Thread] Current Thread [Next in Thread]