X-Git-Url: http://git.grml.org/?a=blobdiff_plain;f=faq%2Findex.html.tt2;h=f663b70692730b8251839c26b36a63209936fbb3;hb=603f7f81acdae0155e314aa3e99097ba7acc0e0e;hp=d1f0fd262069a60ea05f897f168819ab2cff13ca;hpb=743dd3b76047781ba5e0af60de7aa7dfe1e321a0;p=grml.org.git

diff --git a/faq/index.html.tt2 b/faq/index.html.tt2
index d1f0fd2..f663b70 100644
--- a/faq/index.html.tt2
+++ b/faq/index.html.tt2
@@ -28,7 +28,7 @@
 
         <h1 align="center">FAQ for grml</h1>
 
-        <p><strong>Up2date:</strong> applies to Grml version 2017.05</p>
+        <p><strong>Up2date:</strong> applies to Grml version 2020.06</p>
 
         <p><a name="toc"></a><strong>Index:</strong></p>
 
@@ -88,19 +88,15 @@
         <h3><a name="flavours"></a><a href="#toc">What are grml32 / grml64 and grml96?</a></h3>
 
         <ul>
-          <li>grml32-full: 32bit version (kernel and userspace), ~350MB</li>
-          <li>grml64-full: 64bit version (kernel and userspace), ~350MB</li>
-          <li>grml96-full: multi boot version (featuring the grml32-full and grml64-full ISOs combined on one ISO), ~700MB</li>
+          <li>grml32-full: 32bit version (kernel and userspace)</li>
+          <li>grml64-full: 64bit version (kernel and userspace)</li>
+          <li>grml96-full: multi boot version (featuring the grml32-full and grml64-full ISOs combined on one ISO)</li>
         </ul>
 
         <p>Unless you've a good reason to really choose the 32bit flavour we
-        strongly encourage you to use either the grml64 or the grml96
+        <em>strongly</em> encourage you to use either the grml64 or the grml96
         flavour.</p>
 
-        <p>Please notice that this schema was introduced starting with the
-        downsized Grml release 2011.12. Until then grml96 didn't exist and
-        grml32 was known as just 'grml'.</p>
-
         <h3><a name="grmlsmall"></a><a href="#toc">What is the difference between grml-full and grml-small?</a></h3>
 
         <p>grml-small provides a reduced set of available software compared to
@@ -121,18 +117,16 @@
 
         <h3><a name="releasename"></a><a href="#toc">What about the release name?</a></h3>
 
-        <p>Codename of Grml 2017.05 is "Freedatensuppe", which is
-        a wordplay (free data soup) on an austrian dish called <a href="https://de.wikipedia.org/wiki/Frittatensuppe">Frittatensuppe</a>.
-        (We stumbled upon this wordplay through <a href="https://twitter.com/shroombab/status/715650750689517568">a tweet from Barbara Wimmer</a>,
-        referencing a flyer based on a <a href="https://zwerkstatt.at/index.php/produkt/freedaten_h_indiaink/">shirt by zwerkstatt</a>.</p>
+        <p>Codename of Grml 2020.06 is &quot;Ausgehfuahangl&quot;, which is
+	an austrian word for a face mask.</p>
 
         <h3><a name="requirements"></a><a href="#toc">Requirements for running Grml</a></h3>
 
         <ul>
 
-          <li>Intel-compatible CPU (i586 or later, preferably Pentium class or higher)</li>
+          <li>Intel-compatible CPU (i686 or later, preferably Pentium class or higher; although some i586 processors e.g. the 'AMD Geode' are still supported)</li>
 
-          <li>&gt;=256MB of RAM (&gt;=512MB recommended)</p>
+          <li>&gt;=384MB of RAM (&gt;=512MB recommended)</p>
 
           <li>either a bootable CD-/DVD-ROM drive,
           a <a href="#usbboot">USB-boot capable system</a> or a
@@ -152,7 +146,7 @@
         href="http://git.grml.org/?p=grml-live.git;a=blob_plain;f=templates/GRML/grml-cheatcodes.txt;hb=HEAD">grml-cheatcodes
         file</a> (also available via <a href="http://grml.org/cheatcodes/">grml.org/cheatcodes/</a>). Of
         course <a
-        href="http://www.kernel.org/doc/Documentation/kernel-parameters.txt">kernel-parameters.txt</a>
+        href="https://www.kernel.org/doc/html/latest/admin-guide/kernel-parameters.html">the command-line parameters</a>
         of the Linux kernel applies to Grml as well.</p>
 
         <h3><a name="systemd"></a><a href="#toc">Why is Grml using systemd?</a></h3>
@@ -280,11 +274,17 @@ grml keyboard=de xkeyboard=de lang=at # enter this at the bootprompt
         <h3><a name="lvm"></a><a href="#toc">Where are my LVM devices?</a></h3>
 
         <p>LVM (Logival Volumes) is <strong>not</strong> started by default to
-        avoid any possible damage to your data. To get access to present LVM
-        devices just execute:</p>
+        avoid any possible damage to your data. To activate present LVM
+        devices execute (replace "$name" with the name of the PV):</p>
 
 <pre class="rahmen">
-# /etc/init.d/lvm2 start
+# Start lvm2-pvscan@$name
+</pre>
+
+        <p>or if you don't know its name and to enable all present ones, use:</p>
+
+<pre class="rahmen">
+# vgchange -ay
 </pre>
 
         <p>If you want to enable LVM by default just boot using the 'lvm'
@@ -297,7 +297,7 @@ grml keyboard=de xkeyboard=de lang=at # enter this at the bootprompt
         your data. To get access to present SW-RAID devices just execute:</p>
 
 <pre class="rahmen">
-# /etc/init.d/mdadm-raid start
+# mdadm --asssemble --scan
 </pre>
 
         <p>If you want to enable SW-RAID by default just boot using
@@ -340,13 +340,12 @@ grml keyboard=de xkeyboard=de lang=at # enter this at the bootprompt
         <h3><a name="timezone"></a><a href="#toc">How do I configure
         timezone on my Grml system?</a></h3>
 
-        <p>Available bootoptions relevant in live-cd mode:</p>
+        <p>Available bootoptions relevant in live mode:</p>
 
         <ul>
-          <li>utc: set UTC, if your system clock is set to UTC (GMT)
-          <li>gmt: set UTC, if your system clock is set to UTC (GMT) [like bootoption utc]
-          <li>tz=$option: set timezone to corresponding $option, usage example:
-              tz=Europe/Vienna
+          <li>utc: set UTC, if your system/hardware clock is set to UTC (Coordinated Universal Time)
+	  <li>localtime: Hardware Clock is set to local time (LOCAL), this is the default
+          <li>tz=$option: set timezone to corresponding $option, usage example: tz=Europe/Vienna, defaults to UTC if unset
         </ul>
 
         <p>Further information: manpages hwclock(8), tzselect(1) and tzconfig(8); <a
@@ -357,17 +356,9 @@ grml keyboard=de xkeyboard=de lang=at # enter this at the bootprompt
 
         <h3><a name="hdinstall"></a><a href="#toc">Is it possible to install Grml to harddisk?</a></h3>
 
-        <p>Short anwer: No.</p>
-
-        <p>If you want to get a plain Debian system take a look at <a
-        href="/grml-debootstrap/">grml-debootstrap</a>.</p>
-
-        <p>Long(er) answer: yes it's possible to install Grml. But it's not
-        supported and you'll be on your own. That's why we decided to make it
-        not-so-obvious. If you really know what you're doing you'll find out on
-        your own. Reminder: use <a
-        href="/grml-debootstrap/">grml-debootstrap</a> or <a
-        href="http://www.debian.org/">Debian Installer</a> instead.</p>
+        <p>No. If you want to get a Debian system take a look at <a
+        href="/grml-debootstrap/">grml-debootstrap</a> (or use the <a
+        href="https://www.debian.org/">Debian Installer</a> instead).</p>
 
         <h2><a name="software"></a><a href="#toc">Software</a></h2>
 
@@ -407,8 +398,8 @@ grml keyboard=de xkeyboard=de lang=at # enter this at the bootprompt
 
         <p>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 <a href="/contact/">touch with us</a>.</p>
 
       </div>