Hi
I'm using up-to-date Fedora 16 x86_64 KDE spin (from fresh install, not upgrade) and recently I've discover, that 'boot to other os' option is missing. I've got proper configured 'grub2' in 'System Settings -> Login Screen', also I've added 'GDUB_DEFAULT=saved' to /etc/default/grub, but there's no 'arrow' near 'reboot button'. Anybody tried to solve that issue?
Łukasz Redynk wrote:
Hi
I'm using up-to-date Fedora 16 x86_64 KDE spin (from fresh install, not upgrade) and recently I've discover, that 'boot to other os' option is missing. I've got proper configured 'grub2' in 'System Settings -> Login Screen', also I've added 'GDUB_DEFAULT=saved' to /etc/default/grub, but there's no 'arrow' near 'reboot button'. Anybody tried to solve that issue?
For starters, selinux doesn't allow this kde/grub integration by default.
come to think of it, I've never tested this since upgrading away from f15/grub1 ... and I'm pretty sure kdm doesn't support grub2 this way yet.
-- rex
Łukasz Redynk wrote:
I'm using up-to-date Fedora 16 x86_64 KDE spin (from fresh install, not upgrade) and recently I've discover, that 'boot to other os' option is missing. I've got proper configured 'grub2' in 'System Settings -> Login Screen', also I've added 'GDUB_DEFAULT=saved' to /etc/default/grub, but there's no 'arrow' near 'reboot button'. Anybody tried to solve that issue?
http://ksmanis.wordpress.com/2012/01/29/grub2burg-integration-in-kde/
It looks like the upstream code is hardcoding paths which are wrong for Fedora, it can be worked around with symlinks, but we should probably patch the code.
Kevin Kofler
On Sun, Jan 29, 2012 at 05:13, Kevin Kofler kevin.kofler@chello.at wrote:
Łukasz Redynk wrote:
I'm using up-to-date Fedora 16 x86_64 KDE spin (from fresh install, not upgrade) and recently I've discover, that 'boot to other os' option is missing. I've got proper configured 'grub2' in 'System Settings -> Login Screen', also I've added 'GDUB_DEFAULT=saved' to /etc/default/grub, but there's no 'arrow' near 'reboot button'. Anybody tried to solve that issue?
http://ksmanis.wordpress.com/2012/01/29/grub2burg-integration-in-kde/
It looks like the upstream code is hardcoding paths which are wrong for Fedora, it can be worked around with symlinks, but we should probably patch the code.
Even better would be if upstream could add it into the cmake configuration. E.g (untested):
find_file( GRUB2_BURG_CONFIGURATION_FILE NAMES grub2.cfg burg.cfg grub.cfg PATHS "/boot/grub2" "/boot/burg" "/boot/grub" "/etc" DOC "Path to grub2 or burg configuration file" NO_DEFAULT_PATH )
set_property( SOURCE ${grub_relatedsources} APPEND PROPERTY COMPILE_DEFINITIONS "GRUB2_BURG_CONFIGURATION_FILE=${GRUB2_BURG_CONFIGURATION_FILE}" )
I don't know why this kind of thing isn't done more often. Short, simple, easy to set from the command line if needed.
If this looks vaguely sane/wanted i can file a bug upstream suggesting this.
John5342 wrote:
find_file( GRUB2_BURG_CONFIGURATION_FILE NAMES grub2.cfg burg.cfg grub.cfg PATHS "/boot/grub2" "/boot/burg" "/boot/grub" "/etc" DOC "Path to grub2 or burg configuration file" NO_DEFAULT_PATH )
Ugh, find_file is a very bad way to handle this! We normally build packages in a chroot (and I guess several other distros do the same). There is not necessarily any bootloader installed at all in the chroot.
This needs to be a CMake variable settable from the command line (i.e. from our specfile), with find_file only as a fallback.
Kevin Kofler
On Mon, Jan 30, 2012 at 05:24, Kevin Kofler kevin.kofler@chello.at wrote:
John5342 wrote:
find_file( GRUB2_BURG_CONFIGURATION_FILE NAMES grub2.cfg burg.cfg grub.cfg PATHS "/boot/grub2" "/boot/burg" "/boot/grub" "/etc" DOC "Path to grub2 or burg configuration file" NO_DEFAULT_PATH )
Ugh, find_file is a very bad way to handle this! We normally build packages in a chroot (and I guess several other distros do the same). There is not necessarily any bootloader installed at all in the chroot.
This needs to be a CMake variable settable from the command line (i.e. from our specfile), with find_file only as a fallback.
Actually that situation is already covered. Anybody building themselves (no packaging) the file will likely be present and all is automatic. For us packagers we can "BuildRequire: grub2" and we would pick up /etc/grub2.cfg automatically or if we want more control the find_file command automatically creates a cache variable with the DOC string so if we want better control it command line configuration is provided for free. This is one of the few things i actually properly like about CMake.
John5342 wrote:
Actually that situation is already covered. Anybody building themselves (no packaging) the file will likely be present and all is automatic. For us packagers we can "BuildRequire: grub2" and we would pick up /etc/grub2.cfg automatically or if we want more control the find_file command automatically creates a cache variable with the DOC string so if we want better control it command line configuration is provided for free. This is one of the few things i actually properly like about CMake.
Ah right, you can force a preset result for a find_file, which makes my objection moot, sorry for that. (Cool feature indeed.) :-)
Kevin Kofler
-
John5342 -
Kevin Kofler -
Rex Dieter -
Łukasz Redynk