Re: grub as coreboot payload
Hi Robert, >Is that coreboot v2 or v3? coreboot v2, v3 seems to be kind of depreciated and merged into v2. >Which module selection? I chose the modules as given in the wiki ( http://grub.enbug.org/CoreBoot ), topic "Building Coreboot with GRUB2 payload" near the bottom of the page. First I tried to run corboot on real hardware with modules: MODULES="normal ls cat help ext2 iso9660 reiserfs xfs fat pc gpt ata serial memdisk multiboot linux minicmd configfile search tar at_keyboard" as stated at the top of the wiki page. After this failed, I tried as explained with qemu and the iso-image (box at bottom of wiki page), because this worked for me a few months ago. >Did you check the local console? :-) What do you mean with local console? Nothing appeared on the qemu screen, so I switched (ctrl-alt-3) to qemu's serial console. Regards, Andi ___ Grub-devel mailing list Grub-devel@gnu.org http://lists.gnu.org/mailman/listinfo/grub-devel
Any tutorial to configure grub menu interface ?
I wonder if there is any tutorial to crate cool grub menu interface. Can we use the grub2 2009 summer project to get those fancy interfaces ? Thanks ___ Grub-devel mailing list Grub-devel@gnu.org http://lists.gnu.org/mailman/listinfo/grub-devel
Re: [GITGRUB] New menu interface (implementation)
Hi,
Update:
Support password dialog.
In grub.cfg, config users, for example:
set superusers=admin
password admin admin
password user user
In this example, there are two uses admin and user, admin is a superuser.
To set authorized user for a boot item defined with menuentry statement:
menuentry "AA" --users user {
boot
}
To set authorized user for a boot item defined with menu config:
menu {
"AA" {
users = user
command = true
}
}
You can also limit commands in onkey section to be run by super users
only, to do this, add * as the first character. For example:
onkey {
e = "*menu_edit dialog_edit text=command"
t = "if menu_edit dialog_edit text=title; then menu_refresh; fi"
c = "*menu_popup term_window"
f6 = menu_next_anchor
f7 = "menu_popup layout_test"
f8 = menu_toggle_mode
f9 = halt
f10 = reboot
}
e and c hotkey can only be used by super user.
--
Bean
My repository: https://launchpad.net/burg
___
Grub-devel mailing list
Grub-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/grub-devel
Re: Any tutorial to configure grub menu interface ?
On Tue, Oct 27, 2009 at 10:41 PM, J. Bakshi wrote: > I wonder if there is any tutorial to crate cool grub menu interface. Can we > use the grub2 2009 summer project to get those fancy interfaces ? Hi, There are actually two menu system. Colin has written a fancy menu patch as part of gsoc project, you can still get the code from http://grub.gibibit.com/, there are also some docs there. It looks good, but a little slow, and some feature like edit boot command hasn't been implemented. Recently, I have rewritten the menu system and it's almost done by now. The project is hosted at https://launchpad.net/burg, you can also follow this post in ubuntu forum: http://ubuntuforums.org/showthread.php?t=1248647 I plans to add some doc on menu config soon. -- Bean My repository: https://launchpad.net/burg ___ Grub-devel mailing list Grub-devel@gnu.org http://lists.gnu.org/mailman/listinfo/grub-devel
Re: My personal repository
Bean wrote: > On Mon, Oct 26, 2009 at 5:20 AM, Vladimir 'phcoder' Serbinenko > wrote: > >> Bean wrote: >> >>> Hi, >>> >>> I have switched from git to bzr, the repository is moved from github >>> to launchpad: >>> >>> https://launchpad.net/burg >>> >>> >>> >> Hello.Would you consider using bzr.sv.gnu.org rather than launchpad for >> this? This would make collaboration easier. In fact I'm interested in >> merging your changes that are usable into experimental >> > > Hi, > > I choose launchpad as it supports to build ppa binary package. bzr can > pull code from different domain so launchpad should be no different > than savannah. > > Could you then at least send me the notifications for features you think are reasonably ok for experimental? Not having it on same repo makes it more difficult for me to have an overview. I will be unavailable for about a week starting from Thursday. Could you prepare a list of what I should look at for the weekend of 7th November? -- Regards Vladimir 'phcoder' Serbinenko Personal git repository: http://repo.or.cz/w/grub2/phcoder.git ___ Grub-devel mailing list Grub-devel@gnu.org http://lists.gnu.org/mailman/listinfo/grub-devel
grub-1.97
I am putting grub2 into the Linux From Scratch book and have built/tested it and it works quite well for us. Thank you. I do have a question. After building a package, we like to test it for those packages that have tests built in. When I tried `make test`, I got an error about missing m2c. I then went to the Debian repository and built m2c. Now I get the error: bdu...@core2:/usr/src/grub/grub-1.97$ make test m2c-o test -e test test.mod m2c: unknown flag `-e' make: *** [test] Error 1 What version of m2c are you using and where is it available? Is this a valid way to run a regression test for grub-1.97? I'd also like to make a comment. It may be useful if you split up the build into subdirectories by component. When I extracted the tarball, there were 57 files/directories in the top of the build tree. After configure it was 64. So far so good. However, after make it was over 2400 files, many with very long file names. This makes it almost impossible to navigate form the command line, even on a very big screen. If you split it up, you could also shorten the filenames. I would think that would be an advantage to encourage programmers to read the code and contribute to the project. -- Bruce Dubbs linuxfromscratch.org ___ Grub-devel mailing list Grub-devel@gnu.org http://lists.gnu.org/mailman/listinfo/grub-devel
os-prober incorrectly generates stanza - wrong root= device.
While detecting other kernels, update-grub generates the following:
menuentry "Debian GNU/Linux, kernel 2.6.24-etchnhalf.1-686 (on /dev/sda12)" {
insmod ext2
set root=(hd0,12)
search --no-floppy --fs-uuid --set 042b6b67-5464-426e-a60a-21b71dfbcb74
linux /boot/vmlinuz-2.6.24-etchnhalf.1-686 root=/dev/hda5 ro
initrd /boot/initrd.img-2.6.24-etchnhalf.1-686
}
menuentry "Debian GNU/Linux, kernel 2.6.24-etchnhalf.1-686 (single-user mode)
(on /dev/sda12)" {
insmod ext2
set root=(hd0,12)
search --no-floppy --fs-uuid --set 042b6b67-5464-426e-a60a-21b71dfbcb74
linux /boot/vmlinuz-2.6.24-etchnhalf.1-686 root=/dev/hda5 ro single
initrd /boot/initrd.img-2.6.24-etchnhalf.1-686
}
/dev/sda12 is the correct partition, which is correctly reported in the
menuentry and set root= statements, but not on the linux statement.
The result, when trying to boot these entries, is that another system
which has its /root & /root/boot on /dev/sda5 is booted instead.
This happens with grub 1.97 as shipped by ubuntu 9.10.
Not sure this qualifies as a bug, or just incorrect setup my end.
Thanks,
CJ
___
Grub-devel mailing list
Grub-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/grub-devel
