| Re: Re: Re: Problems building on Fedora.
Mar 20 2012 on content Grub2 Kcm |
Ok, the latest git version contains lots of fixes targeted specifically at Fedora 17, plus some other improvements. I tested it quickly in a VM, but the feedback of a day-to-day user would be useful. |
|  | | Re: Re: Re: Problems building on Fedora.
Mar 20 2012 on content Grub2 Kcm |
Ah, just noticed that Fedora no more provides update-grub :-(
So you will also need to create /usr/sbin/update-grub with the following contents:
#!/bin/sh
set -e
exec grub-mkconfig -o /boot/grub2/grub.cfg
and set it executable (chmod 0755 /usr/sbin/update-grub) |
| | | Re: Re: Re: Problems building on Fedora.
Mar 20 2012 on content Grub2 Kcm |
Just tried Fedora 17 in a virtual machine. The problem is that Fedora now installs grub.cfg under /boot/grub2 instead of /boot/grub, and grub-mkconfig as grub2-mkconfig. I will fix this in the next version, for now you can do (in a terminal as root)
cd /boot/grub
ln -s ../grub2/grub.cfg grub.cfg
cd /usr/sbin
ln -s grub2-mkconfig grub-mkconfig
The first time you will still be prompted about wrong permissions, but after entering your password it will work. |
| | | Re: Problems building on Fedora.
Mar 17 2012 on content Grub2 Kcm |
Hi jakepbg, and sorry for the delay. Does it help if you add
#include <unistd.h>
at the top of helper.cpp? |
| | | Re: Well done
Jan 17 2012 on content Win Classic |
Thanks! |
| | | Good!
Apr 12 2011 on content FanSpeed |
Very useful. Thanks! |
| | | Re: Re: Re: grub.cfg fixperm
Mar 26 2011 on content Grub2 Kcm |
The automatic read slot seems a really good idea, although it would probably need some checks to avoid potential security risks. It may be good also for the other part of the module requiring root access: vbetest (currently in git). I'll work on it for v1.4.
I have seen your work, that's very good, Linux is all about choice.
Alberto |
| | | Re: grub.cfg fixperm
Mar 26 2011 on content Grub2 Kcm |
Hi, thanks for your constructive comment. I'll try to explain what's behind this decision.
First of all, I think setting grub.cfg to 0400 is useless anyway, since
1) one can simply read the password directly from the scripts in grub.d
2) if you have direct access to the machine, you can easily get the password with a bunch of techniques, it won't be a 400 to stop you (and crypting the disk will be useless in this case, since /boot cannot be crypted).
Second, that's why I added support for sha512 crypted passwords: anyone considering security so important would never use cleartext ones.
Fixperm is designed to avoid to annoy the user with UAC-style messsages, and since you probably won't be running grub-mkconfig manually everyday (probably just when installing a new kernel) I think it does its job.
That said, since kde it's all about giving the user the power to judge and decide, I'm likely going to add an option to disable it in version 1.4 (1.3 is in string freeze now).
Alberto |
| |
Search people
Current visitors
New users
Birthdays
Most active users
Back
|
|
