From d62a8096c12b4fce8ad700992007494a86ea2189 Mon Sep 17 00:00:00 2001 From: Darshaka Pathirana Date: Wed, 24 Jun 2020 23:03:10 +0200 Subject: [PATCH] Update faq for new stable release 2020.06 --- faq/index.html.tt2 | 90 +++++++++++++++++++++++++++++------------------------- 1 file changed, 49 insertions(+), 41 deletions(-) diff --git a/faq/index.html.tt2 b/faq/index.html.tt2 index 259b45c..f2d81cc 100644 --- a/faq/index.html.tt2 +++ b/faq/index.html.tt2 @@ -40,7 +40,7 @@
  • What does Grml mean?
  • What about the release name?
  • Requirements for running Grml
    • -
  • Which bootoptions does Grml support?
    • +
  • Which boot options does Grml support?
  • Why is Grml using systemd?
  • Are there any known issues with this release? How about reporting bugs?
    • @@ -139,7 +139,7 @@

    The Grml kernel includes support for speakup. For software, brltty and espeakup are included.

    -

    Which bootoptions does Grml support?

    +

    Which boot options does Grml support?

    Check out the grml-cheatcodes @@ -162,7 +162,7 @@ tracking new features/services, but also solve any possible issues around it - duplicating efforts and wasting developers time unnecessarily. Lately we also started to see problems that no one else - seemed to have (or care about enough), for example with multiple network + seemed to have (or cared about enough), for example with multiple network cards we ran into race-conditions with resolvconf. Problems like that turned out to be release stoppers for us.

    @@ -173,35 +173,39 @@ get a fast boot procedure) and identifying failed service startups with sysvinit/file-rc was always hard, unreliable or even impossible under certain conditions. bootlogd was unreliable (while `journalctl -b` is - available out-of-the-box with systemd), bootchart not nicely integrated + available out-of-the-box with systemd), bootchart was not nicely integrated (while systemd-analyze blame/critical-chain works out-of-the-box) and we - aren't aware of any equivalence for e.g. `systemctl --failed`.

    + aren't aware of any equivalence for e.g. + `systemctl --failed`.

    -

    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 existence and more than happy about development and support by Debian's systemd folks.

    +

    With the Grml release 2020.06 we consider the migration of our stack + to systemd as complete. If you encounter problems please i + file a bug and let us know.

    +

    Are there any known issues? How about reporting bugs?

    @@ -214,10 +218,10 @@

    How do I boot Grml from a USB stick?

    Check - out grml2usb - at the - usb webpage in the - grml-wiki.

    + out the Boot Grml from + usb-stick/firewire-device

    Is it possible to store my settings?

    @@ -231,9 +235,9 @@ default for security reasons. Even local logins are not possible (unless you set a password or create new user accounts as root). You can create valid passwords using "sudo - passwd [username]" from the shell individually. To set a password - for users 'root' and 'grml' and enable SSH login you can use the 'ssh' - boot option, like 'ssh=yourpassword'.

    + passwd [username]" from the shell individually. + With the boot option 'ssh' a password for the + users 'root' and 'grml' is and SSH login is enabled.

    How do I find out the version of Grml

    @@ -242,12 +246,15 @@ 
     $ cat /etc/grml_version
    -

    How do I change the language/keyboard settings?

    +

    How do I change the language/keyboard layout?

    + +

    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.

    -

    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:

    +

    Boot option examples:

     grml lang=de      # enter this at the bootprompt and you will get
@@ -256,14 +263,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'.

    Which window managers can I use?

    @@ -287,7 +295,7 @@ grml keyboard=de xkeyboard=de lang=at # enter this at the bootprompt

    If you want to enable LVM by default just boot using the 'lvm' - bootoption which automatically enables LVM.

    + boot option which automatically enables LVM.

    Where are my Software-RAID devices?

    @@ -300,7 +308,7 @@ grml keyboard=de xkeyboard=de lang=at # enter this at the bootprompt

    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.

    @@ -339,13 +347,13 @@ grml keyboard=de xkeyboard=de lang=at # enter this at the bootprompt

    How do I configure timezone on my Grml system?

    -

    Available 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 -- 2.1.4