Slackware This Forum is for the discussion of Slackware Linux.
|
| Notices |
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
 |
GNU/Linux Basic Guide
This 255-page guide will provide you with the keys to understand the philosophy of free software, teach you how to use and handle it, and give you the tools required to move easily in the world of GNU/Linux. Many users and administrators will be taking their first steps with this GNU/Linux Basic guide and it will show you how to approach and solve the problems you encounter.
Click Here to receive this Complete Guide absolutely free. |
|
 |
|
06-24-2012, 02:16 AM
|
#16
|
|
Senior Member
Registered: Aug 2004
Location: Pisa, Italy
Distribution: Slackware
Posts: 1,950
|
just FYI, in the last days, this appeared on gplus (thanks Kay and Harald!): more discussion about it here and here.
|
|
|
|
|
Click here to see the post LQ members have rated as the most helpful post in this thread.
|
06-24-2012, 10:07 AM
|
#17
|
|
Senior Member
Registered: Jan 2011
Location: Oslo, Norway
Distribution: Slackware
Posts: 1,197
|
@ponce, interesting stuff. Thanks for the links!
edit: the link to his loader page is now gone. 
Last edited by ruario; 06-24-2012 at 05:11 PM.
|
|
|
|
06-25-2012, 04:27 PM
|
#18
|
|
Moderator
Registered: Jan 2005
Location: Midwest USA, Central Illinois
Distribution: SlackwareŽ
Posts: 10,358
|
Member Response
Hi,
Quote:
Originally Posted by ponce
just FYI, in the last days, this appeared on gplus (thanks Kay and Harald!): more discussion about it here and here.
|
Great!
I too cannot get to the download. Nor can I find it anywhere. Anyone have it?
|
|
|
|
06-25-2012, 04:50 PM
|
#19
|
|
Slackware Contributor
Registered: Sep 2005
Location: Eindhoven, The Netherlands
Distribution: Slackware
Posts: 4,686
Rep: 
|
Looks like it's been renamed to gummiboot: http://cgit.freedesktop.org/~kay/gummiboot
Eric
|
|
|
|
06-25-2012, 05:11 PM
|
#20
|
|
Senior Member
Registered: Jan 2011
Location: Oslo, Norway
Distribution: Slackware
Posts: 1,197
|
Quote:
Originally Posted by rwebber
It would be nice if the next version of Slackware has the EFI frame buffer turned on,
|
It looks like the first part of your wish came true.
Quote:
Originally Posted by rwebber
and comes with elilo properly configured.
|
hopefully this will happen as well.
|
|
|
|
06-25-2012, 05:13 PM
|
#21
|
|
Senior Member
Registered: Jan 2011
Location: Oslo, Norway
Distribution: Slackware
Posts: 1,197
|
Quote:
Originally Posted by Alien Bob
|
Something to consider for extra? Or perhaps too untested at this stage?
|
|
|
|
06-25-2012, 05:25 PM
|
#22
|
|
Moderator
Registered: Jan 2005
Location: Midwest USA, Central Illinois
Distribution: SlackwareŽ
Posts: 10,358
|
Member Response
Hi,
Yes, I found: git://people.freedesktop.org/~kay/gummiboot
I will check it out later this evening.
Code:
Excerpt from README;
Simple UEFI boot loader which executes configured EFI images, where the
default entry is selected by a configured pattern (glob) or an on-screen
menu.
Operates on the EFI System Partition (ESP) only. Configuration file fragments,
kernels, initrds, other EFI images need to reside on the EFS. Linux kernels
need to be built with CONFIG_EFI_STUB to be able to be directly executed as
an EFI image.
Reads simple and entirely generic boot loader configurion files; one
file per boot loader entry to select from.
Pressing the space (or most other) keys during bootup will show
an on-screen menu with all configured loader entries to select from.
Pressing enter on the selected entry loads and starts the EFI image.
If no timeout is configured and no key pressed during bootup, the default
entry is booted right away.
The config files should be named like:
(ESP)/loader/entries/<vendor>-<release>.conf
$ cat /boot/loader/entries/fedora-3.5.4-1.fc18.x86_64.conf
title Fedora 18 (3.5.4-1.fc17.x86_64)
linux /fedora/vmlinuz-3.5.4-1.fc17.x86_64
initrd /fedora/initrd-3.5.4-1.fc17.x86_64
options root=UUID=f8f83f73-df71-445c-87f7-31f70263b83b
$ cat /boot/loader/entries/custom-kernel.conf
title My test Kernel - without initramfs
options root=PARTUUID=084917b7-8be2-4e86-838d-f771a9902e08
linux /bzImage
$ cat /boot/loader/entries/redhat-grub.conf
title GRUB
efi /EFI/redhat/grub2-efi/grub.efi
$ cat /boot/loader/entries/zzz-efi-shell.conf
title EFI Shell
efi /EFI/shell/Shell.efi
Paths are automatically converted from '/' to '\', and a leading '\' is
added if needed.
Loader options can be stored in:
(ESP)/loader/loader.conf
$ cat /boot/loader/loader.conf
timeout 10
default fedora-*
The timeout is specified in seconds, the default is 0, which suppresses the
menu. If a timeout is given, in the config file or in the EFI variable
"LoaderConfigTimeout", the on-screen menu with the default entry selected is
shown, and a timer counting downwards.
Pressing the '+' or '-' key in the menu will set or clear a custom timeout
value. The setting is stored persistently in the EFI variable "LoaderConfigTimeout".
The default entry is selected by a pattern match on the configuration file
names. The matched strings are basenames of the config files translated to
lowercase and without the ".conf" suffix. The last matching entry in the
sorted list is selected. If no match pattern is specified, the last entry in
the list is selected.
This will automatically select the latest Fedora kernel entry:
default fedora-*
This will automatically select the latest Fedora 18 kernel:
default fedora-*.fc18.*
Pressing the 'd' key in the menu will mark the selected entry as the default
boot entry. The entry is identified by a leading '*'. Pressing the 'd' key again
will clear the setting. The setting is stored persistently in the EFI variable
"LoaderConfigDefault".
The EFI variable LoaderEntryOneShot= can be used to specify a loader entry
for the next and only the next reboot. The variable will always be cleared
directly after it is read.
Before executing the selected image, the boot entry indentifier is stored in
the EFI variable "LoaderEntrySelected" and available during runtime at:
/sys/firmware/efi/vars/LoaderEntrySelected-4a67b082-0a4c-41cf-b6c7-440b29bb8c4f/
The allocated random UUID 4a67b082-0a4c-41cf-b6c7-440b29bb8c4f is meant to be
shared across tools which implement the config file layout, format, and the EFI
variables.
Last edited by onebuck; 06-25-2012 at 06:33 PM.
Reason: typo0
|
|
|
|
| Thread Tools |
Search this Thread |
|
|
|
Posting Rules
|
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
HTML code is Off
|
|
|
All times are GMT -5. The time now is 01:36 PM.
|
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|