1 <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">
3 <title>grml.org - FAQ</title>
4 <meta name="Title" content="grml.org - FAQ" />
5 <meta name="Author" content="the grml team [www.grml.org/team/]" />
6 <meta name="Keywords" content="grml.org, grml" />
7 <meta name="Description" content="FAQ of grml.org" />
8 <meta name="Abstract" content="grml, just another linux-distribution" />
9 <meta name="fdse-index-as" content="http://www.grml.org/faq/" />
10 <meta name="Robots" content="index,follow" />
11 <meta name="Language" content="english" />
12 <meta name="identifier-url" content="http://www.grml.org/" />
13 <meta name="MSSmartTagsPreventParsing" content="true" />
14 <meta http-equiv="imagetoolbar" content="no" />
15 <link rel="home" href="/" title="grml.org" />
16 <link rel="help" href="/features/" title="About" />
17 <link rel="author" href="/team/" title="Team" />
18 <link rel="icon" href="/favicon.png" type="image/png" />
19 <link rel="stylesheet" href="/style.css" type="text/css" />
23 [% INCLUDE static.inc %]
27 <p><img style="float: right" src="/img/clanbomber.png" alt="*" /></p>
29 <h1 align="center">FAQ for grml</h1>
31 <p><strong>Up2date:</strong> applies to Grml version 2018.12</p>
33 <p><a name="toc"></a><strong>Index:</strong></p>
35 <p class="toc"><a href="#general">General:</a></p>
37 <li><a href="#whatis">What is Grml?</a></li>
38 <li><a href="#flavours">What are grml32 / grml64 and grml96?</a></li>
39 <li><a href="#grmlsmall">What is the difference between grml-full and grml-small?</a></li>
40 <li><a href="#get">Where do I get Grml?</a></li>
41 <li><a href="#whatmeans">What does Grml mean?</a></li>
42 <li><a href="#releasename">What about the release name?</a></li>
43 <li><a href="#requirements">Requirements for running Grml</a></li>
44 <li><a href="#bootoptions">Which bootoptions does Grml support?</a></li>
45 <li><a href="#systemd">Why is Grml using systemd?</a></li>
46 <li><a href="#known_issues">Are there any known issues with this release? How about reporting bugs?</a></li>
49 <p class="toc"><a href="#features">Features</a>:</p>
51 <li><a href="#usbboot">How do I boot Grml from a USB stick?</a></li>
52 <li><a href="#persistency">Is it possible to store my settings?</a></li>
53 <li><a href="#password">What are the passwords of users on Grml?</a></li>
54 <li><a href="#version">How do I find out the version of Grml</a></li>
55 <li><a href="#language">How do I change the language/keyboard settings?</a></li>
56 <li><a href="#wms">Which window managers can I use?</a></li>
57 <li><a href="#lvm">Where are my LVM devices?</a></li>
58 <li><a href="#swraid">Where are my Software-RAID devices?</a></li>
59 <li><a href="#booting">Which ways exist to boot Grml?</a></li>
60 <li><a href="#timezone">How do I configure timezone on my Grml system?</a></li>
61 <li><a href="#hdinstall">Is it possible to install Grml to harddisk?</a></li>
64 <p class="toc"><a href="#software">Software:</a></p>
66 <li><a href="#sw_version">Which package(s) and which version is available?</a></li>
67 <li><a href="#zsh">Why is Zsh the default shell?</a></li>
71 <p class="toc"><a href="#stuff">Support / Unanswered stuff:</a></p>
73 <li><a href="#questions">Further questions?</a></li>
74 <li><a href="#support">Commercial Support</a></li>
77 <h2><a name="general"></a><a href="#toc">General</a></h2>
79 <h3><a name="whatis"></a><a href="#toc">What is Grml?</a></h3>
81 <p>Grml is a bootable live system (Live-CD) based
82 on <a href="http://www.debian.org/">Debian</a>. It is not
83 necessary to install anything to a harddisk. Grml includes a
84 collection of GNU/Linux software especially for system
85 administrators. It specializes on administrative tasks like
86 installation, deployment and system rescue.</p>
88 <h3><a name="flavours"></a><a href="#toc">What are grml32 / grml64 and grml96?</a></h3>
91 <li>grml32-full: 32bit version (kernel and userspace)</li>
92 <li>grml64-full: 64bit version (kernel and userspace)</li>
93 <li>grml96-full: multi boot version (featuring the grml32-full and grml64-full ISOs combined on one ISO)</li>
96 <p>Unless you've a good reason to really choose the 32bit flavour we
97 <em>strongly</em> encourage you to use either the grml64 or the grml96
100 <h3><a name="grmlsmall"></a><a href="#toc">What is the difference between grml-full and grml-small?</a></h3>
102 <p>grml-small provides a reduced set of available software compared to
103 grml-full. It provides the same Linux kernel image as grml-full and is
104 fully binary compatible. Choose the grml-small flavour if size - for
105 whatever reason - really matters to you.</p>
107 <h3><a name="get"></a><a href="#toc">Where do I get Grml?</a></h3>
109 <p>Grml is open source, you can download it from the mirrors
110 listed at <a href="/download">grml.org/download/</a>.</p>
112 <h3><a name="whatmeans"></a><a href="#toc">What does Grml mean?</a></h3>
114 <p>Grml comes close to 'argl' or 'grrr' in English. People use
115 this when they want to express their dissatisfaction with
116 software (amongst other things).</p>
118 <h3><a name="releasename"></a><a href="#toc">What about the release name?</a></h3>
120 <p>Codename of Grml 2018.12 is "Gnackwatschn", which is
121 an austrian and bavarian word, meaning "hit in the neck".
122 We consider this an alternative to a facepalm; although a "Gnackwatschn" isn't usually self-inflicted.
124 <h3><a name="requirements"></a><a href="#toc">Requirements for running Grml</a></h3>
128 <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>
130 <li>>=384MB of RAM (>=512MB recommended)</p>
132 <li>either a bootable CD-/DVD-ROM drive,
133 a <a href="#usbboot">USB-boot capable system</a> or a
134 network card for booting via network/PXE (check
135 out <a href="#terminalserver">grml-terminalserver</a>)</li>
139 <h3><a name="accessibility"></a><a href="#toc">What does accessibility at Grml mean?</a></h3>
141 <p>The Grml kernel includes support for speakup. For software,
142 brltty and espeakup are included.</p>
144 <h3><a name="bootoptions"></a><a href="#toc">Which bootoptions does Grml support?</a></h3>
147 href="http://git.grml.org/?p=grml-live.git;a=blob_plain;f=templates/GRML/grml-cheatcodes.txt;hb=HEAD">grml-cheatcodes
148 file</a> (also available via <a href="http://grml.org/cheatcodes/">grml.org/cheatcodes/</a>). Of
150 href="https://www.kernel.org/doc/html/latest/admin-guide/kernel-parameters.html">the command-line parameters</a>
151 of the Linux kernel applies to Grml as well.</p>
153 <h3><a name="systemd"></a><a href="#toc">Why is Grml using systemd?</a></h3>
155 <p>The switch from file-rc to systemd happened for various reasons.
156 Grml used file-rc for many years, mainly because it provided a better
157 way to control startup behavior via its /etc/runlevel.conf configuration
158 than with using sysvinit. Though for us Grml developers this also meant
159 that whenever there have been any changes in Debian's startup
160 configuration we had to compare our /etc/runlevel.conf setup with what a
161 normal Debian system would give us. Users who wanted to remaster Grml
162 with a custom startup procedure as well had to practically fork
163 maintenance of the /etc/runlevel.conf file. This didn't only mean
164 tracking new features/services, but also solve any possible issues
165 around it - duplicating efforts and wasting developers time
166 unnecessarily. Lately we also started to see problems that no one else
167 seemed to have (or care about enough), for example with multiple network
168 cards we ran into race-conditions with resolvconf. Problems like that
169 turned out to be release stoppers for us.</p>
171 <p>systemd on the other hand provides great documentation, service
172 supervision, takes care of parallel service startup and is the default
173 init system on most Linux distributions nowadays. This means more users,
174 better testing and integration. Logging, startup time investigation (to
175 get a fast boot procedure) and identifying failed service startups with
176 sysvinit/file-rc was always hard, unreliable or even impossible under
177 certain conditions. bootlogd was unreliable (while `journalctl -b` is
178 available out-of-the-box with systemd), bootchart not nicely integrated
179 (while systemd-analyze blame/critical-chain works out-of-the-box) and we
180 aren't aware of any equivalence for e.g. `systemctl --failed`.</p>
182 <p>While migrating our stack to systemd is <em>not</em> fully finished
183 yet, its switch - at least so far - was easier than expected. It also
184 turns out that it gives users who want to remaster Grml (or build their
185 very own ISOs from scratch using grml-live) more flexibility and control
186 over the startup process. systemd's override.conf mechanism and preset
187 feature provides the flexibility to overwrite unwanted behavior, without
188 losing the option to use existing defaults.</p>
190 <p>Last but not least we think it's good that systemd is actively
191 maintained and receives attention. The sysvinit/file-rc ecosystem was
192 stagnating/non-existend for too many years. Grml used its own initrd
193 implementation in its very beginnings, until a more broadly available
194 initramfs-tools/ live-boot solution appeared, broadening the user base,
195 sharing goals amongst different (live) distributions. Back in the days
196 Grml - like many other live distributions - had to implement hardware
197 recognition on its own. While udev received lots of complaints back
198 then, its integration actually solved all the hardware recognition for
199 the good. systemd's vision of stateless systems is something which helps
200 building live systems like Grml.</p>
202 <p>While we don't claim that systemd is perfect and doesn't have its
203 issues and drawbacks (like any software), we're happy about its
204 existence and more than happy about development and support by Debian's
207 <a name="release"></a> <!-- old anchor -->
208 <a name="bugreport"></a> <!-- old anchor -->
209 <h3><a name="known_issues"></a><a href="#toc">Are there any known issues? How about reporting bugs?</a></h3>
211 <p>Please visit the <a href="/bugs/">bug webpage</a>.</p>
213 <h2><a name="features"></a><a href="#toc">Features</a></h2>
215 <!-- TODO: needs to be improved! -->
216 <h3><a name="usbboot"></a><a href="#toc">How do I boot Grml from a USB stick?</a></h3>
219 out <a href="http://wiki.grml.org/doku.php?id=usb#grml2usb">grml2usb</a>
221 <a href="http://wiki.grml.org/doku.php?id=usb">usb webpage in the
224 <h3><a name="store"></a><a name="persistency"></a><a href="#toc">Is it possible to store my settings?</a></h3>
227 a <a href="http://wiki.grml.org/doku.php?id=persistency">persistency
230 <h3><a name="password"></a><a href="#toc">What are the passwords of users on Grml?</a></h3>
232 <p>There are no default passwords - all accounts are locked by
233 default for security reasons. Even local logins are not
234 possible (unless you set a password or create new user
235 accounts as root). You can create valid passwords using "sudo
236 passwd [username]" from the shell individually. To set a password
237 for users 'root' and 'grml' and enable SSH login you can use the 'ssh'
238 boot option, like 'ssh=yourpassword'.</p>
240 <h3><a name="version"></a><a href="#toc">How do I find out the version of Grml</a></h3>
242 <p>Run 'grml-version' or use the following command:</p>
245 $ cat /etc/grml_version</pre>
247 <h3><a name="language"></a><a href="#toc">How do I change the language/keyboard settings?</a></h3>
249 <p>By default Grml uses english settings. But it is possible to
250 change the settings via using either the bootparam(s) lang,
251 keyboard and xkeyboard or via executing grml-lang when Grml is
252 already running. Usage examples:</p>
255 grml lang=de # enter this at the bootprompt and you will get
256 # german keyboard layout and german $LANG, $LC_ALL,
258 grml keyboard=de xkeyboard=de lang=at # enter this at the bootprompt
259 # and you will get german keyboard and austrian
261 % grml-lang de # enter this in the shell to switch keyboard layout
262 # and $LANG settings in a running Grml system
265 <p>Note: run grml-setlang to get a dialog based frontend for
266 /etc/default/locale. Run grml-setkeyboard to get a dialog
267 based frontend for /etc/sysconfig/keyboard.</p>
270 <h3><a name="wms"></a><a href="#toc">Which window managers can I use?</a></h3>
272 <p>Starting with the 2011.12 release Grml provides <a
273 href="http://www.fluxbox.org/">Fluxbox</a> as window manager.</p>
275 <h3><a name="lvm"></a><a href="#toc">Where are my LVM devices?</a></h3>
277 <p>LVM (Logival Volumes) is <strong>not</strong> started by default to
278 avoid any possible damage to your data. To get access to present LVM
279 devices execute (replace "$name" with the name of the PV):</p>
282 # Start lvm2-pvscan@$name
285 <p>or if you don't know its name, use:</p>
292 <p>If you want to enable LVM by default just boot using the 'lvm'
293 bootoption which automatically enables LVM.</p>
295 <h3><a name="swraid"></a><a href="#toc">Where are my Software-RAID devices?</a></h3>
297 <p>Software-RAID (usually known as the mdadm stuff) is
298 <strong>not</strong> started by default to avoid any possible damage to
299 your data. To get access to present SW-RAID devices just execute:</p>
302 # mdadm --asssemble --scan
305 <p>If you want to enable SW-RAID by default just boot using
306 the 'swraid' bootoption which enables automatic assembling of
307 software raid arrays.</p>
309 <a name="terminalserver"></a>
310 <h3><a name="booting"></a><a href="#toc">Which ways exist to boot Grml?</a></h3>
312 <!-- TODO: needs rework -->
314 <p>Of course running from CD/DVD is a common way to boot
315 Grml. But Grml provides many more ways to boot:</p>
317 <p>It is possible to boot Grml via USB (e.g. USB stick or
318 harddisk), firewire, or running from a Compact Flash disk. It
319 works out of the box; you don't need to modify anything. Check
320 out <a href="http://wiki.grml.org/doku.php?id=usb">the usb
321 webpage in the grml-wiki</a> for more details.</p>
323 <p>Your computer can not boot from CD-ROM but provides a
324 floppy disk? Take a look
325 at <a href="http://btmgr.sourceforge.net/">btmgr</a>, <a href="http://ubcd4win.com/faq.htm#floppy">ubcd4win</a>
326 or <a href="http://linux.simple.be/tools/sbm">sbm</a>. They
327 provide support for booting from CD-ROM via a special floppy
330 <p>grml-terminalserver makes it possible to boot your system
332 using <a href="http://en.wikipedia.org/wiki/Preboot_Execution_Environment">PXE</a>
333 (Preboot Execution Environment). If your network card does not
334 provide support for booting via PXE you can still boot it
335 either using the provided grub image by grml-terminalserver
336 (for example via floppy drive) or
337 using <a href="http://etherboot.org/wiki/index.php">gPXE</a>.
338 For more information, refer to
339 the <a href="/terminalserver/">grml-terminalserver
342 <h3><a name="timezone"></a><a href="#toc">How do I configure
343 timezone on my Grml system?</a></h3>
345 <p>Available bootoptions relevant in live mode:</p>
348 <li>utc: set UTC, if your system/hardware clock is set to UTC (Coordinated Universal Time)
349 <li>localtime: Hardware Clock is set to local time (LOCAL), this is the default
350 <li>tz=$option: set timezone to corresponding $option, usage example: tz=Europe/Vienna, defaults to UTC if unset
353 <p>Further information: manpages hwclock(8), tzselect(1) and tzconfig(8); <a
354 href="http://www.debian.org/doc/manuals/system-administrator/ch-sysadmin-time.html">Debian
355 GNU/Linux System Administrator's Manual Chapter 16 - Time</a> and <a
356 href="http://wiki.debian.org/TimeZoneChanges">TimeZoneChanges in the
359 <h3><a name="hdinstall"></a><a href="#toc">Is it possible to install Grml to harddisk?</a></h3>
361 <p>No. If you want to get a Debian system take a look at <a
362 href="/grml-debootstrap/">grml-debootstrap</a> (or use the <a
363 href="https://www.debian.org/">Debian Installer</a> instead).</p>
365 <h2><a name="software"></a><a href="#toc">Software</a></h2>
367 <h3><a name="sw_version"></a><a href="#toc">Which package(s) and which
368 version is available?</a></h3>
370 <p>If you want to get details about the provided packages and the
371 package versions without booting the Grml ISO check out the dpkg_...
372 files in the <a href="/files/#debian">Debian-Information section on
373 grml.org/files/</a>.</p>
375 <h3><a name="zsh"></a><a href="#toc">Why is Zsh the default shell?</a></h3>
377 <p>Short answer: because <a href="/zsh/">Zsh rocks</a>, really!</p>
379 <p>Long(er) answer: If you don't know Zsh take a look the <a
380 href="/zsh/">Grml Zsh reference card</a>.</p>
382 <p>If you are a Bash user and don't know Zsh yet, don't be
383 afraid. Bash is largely a subset of Zsh and you don't have to
384 throw away your knowledge about shell stuff.</p>
386 <h2><a name="stuff"></a><a href="#toc">Support / Unanswered stuff</a></h2>
388 <h3><a name="questions"></a><a href="#toc">Further questions</a></h3>
390 <p>Do you have a question which is not answered in the FAQ or
391 in the provided <a href="/docs/">documentation</a> (execute
392 "grml-info" on your Grml system for offline
393 documentation)? Also check out 'grml-tips $KEYWORD' on your
394 Grml system. Take a look at
395 <a href="/">the Grml website</a> and <a href="http://wiki.grml.org/">the
396 grml-wiki</a>. A good place to become part of the community is the <a
397 href="/mailinglist/">Grml mailinglist</a>.</p>
399 <h3><a name="support"></a><a href="#toc">Commercial Support</a></h3>
401 <p>You want to deploy Grml in your data center, use it as part of your
402 business or have an emergency case? You're happy with Grml but would
403 like to get your very own live cd (providing your favourite software
404 selection, special configuration, setup and your bootsplash)?
405 Please get in <a href="/contact/">touch with us</a>.</p>
409 [% INCLUDE static_bottom.inc %]