Up2date: applies to Grml version 2018.12
+Up2date: applies to Grml version 2024.02
@@ -41,7 +40,7 @@Codename of Grml 2018.12 is "Gnackwatschn", which is - an austrian and bavarian word, meaning "hit in the neck". - We consider this an alternative to a facepalm. +
Codename of Grml 2024.02 is "Glumpad". + This is an austrian word for odds and ends, bits and pieces, useless stuff. + Related words in Austrian are "Klumpert" and "Krimskrams", though the 'glum' and 'pad' might make the pronunciation more interesting.
The Grml kernel includes support for speakup. For software, brltty and espeakup are included.
-While migrating our stack to systemd is not fully finished - yet, its switch - at least so far - was easier than expected. It also - turns out that it gives users who want to remaster Grml (or build their - very own ISOs from scratch using grml-live) more flexibility and control +
It also turned out that it gives users who want to remaster Grml (or + build their very own ISOs from scratch using grml-live) more flexibility + and control over the startup process. systemd's override.conf mechanism and preset feature provides the flexibility to overwrite unwanted behavior, without losing the option to use existing defaults.
-Last but not least we think it's good that systemd is actively +
We think it's good that systemd is actively maintained and receives attention. The sysvinit/file-rc ecosystem was - stagnating/non-existend for too many years. Grml used its own initrd + stagnating/non-existent for too many years. Grml used its own initrd implementation in its very beginnings, until a more broadly available - initramfs-tools/ live-boot solution appeared, broadening the user base, + initramfs-tools / live-boot solution appeared, broadening the user base, sharing goals amongst different (live) distributions. Back in the days Grml - like many other live distributions - had to implement hardware - recognition on its own. While udev received lots of complaints back - then, its integration actually solved all the hardware recognition for - the good. systemd's vision of stateless systems is something which helps - building live systems like Grml.
+ recognition on its own. While udev received lots of complaints back + then, its integration actually solved all the hardware recognition + problems for the good. systemd's vision of stateless systems is + something which helps building live systems like Grml.While we don't claim that systemd is perfect and doesn't have its issues and drawbacks (like any software), we're happy about its @@ -215,16 +214,14 @@
Check - out grml2usb - at the - usb webpage in the - grml-wiki.
+Check out the grml2usb manpage + and the grml-wiki page + "Boot Grml from usb-stick/firewire-device".
Yes, using the - a persistency + persistency feature.
$ cat /etc/grml_version-
By default Grml uses english settings. But it is possible to - change the settings via using either the bootparam(s) lang, - keyboard and xkeyboard or via executing grml-lang when Grml is - already running. Usage examples:
+The default language of the Grml system is English (en_US.UTF-8). + All other locales are removed by default. + But it is possible to change the keyboard layout via either using 'grml-quickconfig', + the boot option(s) 'lang', 'keyboard' and 'xkeyboard' + or via executing grml-lang when Grml is already running.
+ +Boot option examples:
grml lang=de # enter this at the bootprompt and you will get
@@ -258,14 +258,15 @@ grml lang=de # enter this at the bootprompt and you will get
grml keyboard=de xkeyboard=de lang=at # enter this at the bootprompt
# and you will get german keyboard and austrian
# language variables
-% grml-lang de # enter this in the shell to switch keyboard layout
- # and $LANG settings in a running Grml system
- Note: run grml-setlang to get a dialog based frontend for - /etc/default/locale. Run grml-setkeyboard to get a dialog - based frontend for /etc/sysconfig/keyboard.
+'grml-lang' example:
+ ++% grml-lang de # enter this in the shell to switch keyboard layout ++
Note: Run 'grml-setlang' to get a dialog based frontend for '/etc/default/locale'.
LVM (Logival Volumes) is not started by default to - avoid any possible damage to your data. To get access to present LVM + avoid any possible damage to your data. To activate present LVM devices execute (replace "$name" with the name of the PV):
# Start lvm2-pvscan@$name-
or if you don't know its name, use:
+or if you don't know its name and to enable all present ones, use:
-# Start lvm2-lvmetad # vgchange -ay
If you want to enable LVM by default just boot using the 'lvm' - bootoption which automatically enables LVM.
+ boot option which automatically enables LVM.If you want to enable SW-RAID by default just boot using - the 'swraid' bootoption which enables automatic assembling of + the 'swraid' boot option which enables automatic assembling of software raid arrays.
@@ -342,13 +342,13 @@ grml keyboard=de xkeyboard=de lang=at # enter this at the bootpromptAvailable bootoptions relevant in live mode:
+Availabe boot options:
-+grml utc # set UTC, if your system/hardware clock is set to UTC (Coordinated Universal Time) +grml localtime # Hardware Clock is set to local time (LOCAL), this is the default +grml tz=$option # set timezone to corresponding $option, usage example: tz=Europe/Vienna, defaults to UTC if unset +
Further information: manpages hwclock(8), tzselect(1) and tzconfig(8); Debian
@@ -400,8 +400,8 @@ grml keyboard=de xkeyboard=de lang=at # enter this at the bootprompt
You want to deploy Grml in your data center, use it as part of your
business or have an emergency case? You're happy with Grml but would
- like to get your very own live cd (providing your favourite software
- selection, special configuration, setup and your bootsplash)?
+ like to get your very own live system (providing your favourite software
+ selection, special configuration, setup and a custom bootsplash)?
Please get in touch with us.