Skip to content

openSUSE/gfxboot

master
Switch branches/tags

Name already in use

A tag already exists with the provided branch name. Many Git commands accept both tag and branch names, so creating this branch may cause unexpected behavior. Are you sure you want to create this branch?
Code

Latest commit

Luna Jernberg and openSUSE Weblate Translated using Weblate (Swedish)
Currently translated at 100.0% (95 of 95 strings)

Translation: gfxboot/master
Translate-URL: https://l10n.opensuse.org/projects/gfxboot/master/sv/
a6a0fb6

Git stats

Files

Permalink
Failed to load latest commit information.
Type
Name
Latest commit message
Commit time
bin
 
 
doc
 
 
jpg
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

gfxboot

About gfxboot

gfxboot is a graphical boot screen for syslinux (up to version 4) and grub1.

Features

  • editable boot options
  • a menu system
  • context sensitive help texts (in html) shown in separate windows
  • support for different keyboard layouts
  • i18n support (localization via po files, Unicode char rendering via freetype lib)
  • text-to-speech support via pc-speaker
  • can run animations and play wav files
  • works via serial line (with text-based menus)

Downloads

Get the latest version from the openSUSE Build Service.

Examples

It is used by openSUSE Tumbleweed. The boot screen looks like this:

openSUSE Tumbleweed boot screen

A more minimalistic example included in the git repository:

example boot screen

openSUSE Development

To build, simply run make. Install with make install.

To build a reference for the stack-based bincode (used in themes/openSUSE/src/*.inc), run

$ make doc
$ xdg-open doc/gfxboot.html || less doc/gfxboot.txt

Basically every new commit into the master branch of the repository will be auto-submitted to all current SUSE products. No further action is needed except accepting the pull request.

Submissions are managed by a SUSE internal jenkins node in the InstallTools tab.

Each time a new commit is integrated into the master branch of the repository, a new submit request is created to the openSUSE Build Service. The devel project is system:install:head.

*.changes and version numbers are auto-generated from git commits, you don't have to worry about this.

The spec file is maintained in the Build Service only. If you need to change it for the master branch, submit to the devel project in the build service directly.

Development happens exclusively in the master branch. The branch is used for all current products.

You can find more information about the changes auto-generation and the tools used for jenkis submissions in the linuxrc-devtools documentation.