X-Git-Url: http://git.grml.org/?a=blobdiff_plain;f=faq%2Findex.html.tt2;h=a8e18ec8c557022a28786de1fc92a273c2cc565a;hb=HEAD;hp=9d791c34cf935c9a12d11c12003a7bb7fa5d6c6d;hpb=cb3b2a1cb2cc12f475f66c163ea09b9dd9071b5b;p=grml.org.git diff --git a/faq/index.html.tt2 b/faq/index.html.tt2 index 9d791c3..0928fa8 100644 --- a/faq/index.html.tt2 +++ b/faq/index.html.tt2 @@ -8,7 +8,7 @@ - + @@ -27,7 +27,7 @@

FAQ for grml

-

Up2date: applies to Grml version 2020.06

+

Up2date: applies to Grml version 2024.02

Index:

@@ -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?
  • @@ -116,8 +116,9 @@

    What about the release name?

    -

    Codename of Grml 2020.06 is "Ausgehfuahangl", which is - an austrian word for a face mask.

    +

    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.

    Requirements for running Grml

    @@ -125,7 +126,7 @@
  • Intel-compatible CPU (i686 or later, preferably Pentium class or higher; although some i586 processors e.g. the 'AMD Geode' are still supported)
  • -
  • >=384MB of RAM (>=512MB recommended)

    +
  • >=576MB of RAM (>=1GB recommended)

  • either a bootable CD-/DVD-ROM drive, a USB-boot capable system or a @@ -139,7 +140,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 +163,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,29 +174,29 @@ 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 @@ -213,16 +214,14 @@

    How do I boot Grml from a USB stick?

    -

    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".

    Is it possible to store my settings?

    Yes, using the - a persistency + persistency feature.

    What are the passwords of users on Grml?

    @@ -231,9 +230,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 +241,15 @@
     $ cat /etc/grml_version
    -

    How do I change the language/keyboard settings?

    +

    How do I change the language/keyboard layout?

    -

    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
    @@ -256,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'.

    Which window managers can I use?

    @@ -287,7 +290,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 +303,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 +342,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