4 <title>grml.org - Survey 2011</title>
5 <meta name="Title" content="grml.org - Survey 2011" />
6 <meta name="Author" content="the grml team [grml.org/team/]" />
7 <meta name="Keywords" content="grml.org, grml" />
8 <meta name="Description" content="Survey 2011 @ grml.org" />
9 <meta name="Abstract" content="grml, just another linux-distribution" />
10 <meta name="Robots" content="index,follow" />
11 <meta name="Language" content="english" />
12 <meta name="identifier-url" content="https://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 <h1><a name="top"></a>Grml User Survey 2011</h1>
31 <p>In the beginning of 2011 we started a Grml user survey. From our
32 point of view it was an overwhelming success. As promised we will
33 share the results and discuss the feedback we got in detail.</p>
35 <p><abbr title="Too long; didn't read">tl;dr</abbr>? Skip to the <a href="#conclusion">conclusion</a>.
36 Interested in <a href="#toc">all the answers</a>?</p>
40 <p>First of all some numbers regarding our user survey. 28
41 questions, answered by more than 300 users in a timeframe of less
42 than one month. This means more than 8000 entries. On the day of the
43 announcement more than 70 people answered our survey. For our last
44 <a href="http://wiki.grml.org/doku.php?id=survey07">user survey back
45 in 2007</a> 103 people answered in one month. Long story short: it
46 was an overwhelming success.</p>
48 <p>Due to the many open questions we got some interesting, fun and
49 exciting answers. We also got some nice use cases for Grml.</p>
51 <p>The overall quality of the provided answers, especially in the
52 custom texts were astonishing and we all enjoyed them.</p>
56 <p>Obviously some questions could have been asked in a better way,
57 for example the DVD question. Instead of asking "should we
58 produce DVD Images" we could have asked if its worthwhile to
59 keep the 700MB limit for the CDs. Nevertheless we now know that a
60 DVD-image is not really important and worthwhile as most of you want
61 to get CD-sized images these days.</p>
63 <p>As we used Google Forms we did not get the IP address of the
64 participant. So we weren't able to gather geographic information
65 about the participants. We fixed this after we noticed the problem
66 by adding another question asking participants about their
69 <p>We did not ask about contact information but it would have been
70 worthwhile in some cases to get back to our users and provide
71 answers or hints. We did not change the survey as we were unsure if
72 its appropriate to ask for contact information in a survey.</p>
74 <p>Most answers did not result in immediate actions but we already
75 discussed the inclusion of provided packages and had a look at
80 <p>We used Google Forms and had many "Other options"
81 available. Unfortunately Google automatically translates predefined
82 labels. This means for e.g. persons from german speaking countries
83 the "Other" label was called "Andere" or the
84 submit button "Absenden". It would be great to disable
85 that feature or provide proper multi language form support in Google
86 Docs. Also the evaluation of custom answers turned out to be a lot
89 <h2><a name="conclusion"></a>Conclusion</h2>
91 <p>Our strong focus on system administration tasks has been affirmed
92 by our users in 2007 and today. We will continue to aim to be the
93 best speciality Debian-based distribution for these use cases.
94 Desktop users will continue to be supported on the same level as
97 <p>While our user base is strong in Europe, we must expand further into
98 US and Asia. A first step, namely new mirrors closer to these
99 regions, has already been made.</p>
101 <p>A lot of awesome software has been suggested and some of it
102 already made it to the daily Grml builds. We will continue to work
103 on adding new software, but the important "One CD" (700MB)
104 limit is obviously a hard barrier. </p>
106 <p>We still want your feedback on all topics, but especially from
107 users of non-Debian-based distros. What do you like, what's missing,
108 what's bad for you? <a href="http://feedback.grml.org/">Send and
109 share your feedback</a> or <a
110 href="http://grml.org/contact/">drop us a message</a>!</p>
112 <p><strong>Thanks to everyone taking part in our survey!</strong></p>
114 <h3><a name="toc"></a>Table of Content - the Answers</h3>
119 <li><a href="#since_when">Since when have you been using Grml?</a></li>
120 <li><a href="#stumble">How did you stumble upon Grml?</a></li>
121 <li><a href="#located">Where are you located?</a></li>
122 <li><a href="#knowledge">Level of Linux knowledge</a></li>
123 <li><a href="#operating_systems">Which operating systems do you use?</a></li>
124 <li><a href="#distributions">If you are using Linux, which distributions do you use?</a></li>
125 <li><a href="#project_name">Did you start your own Open Source project?</a></li>
126 <li><a href="#project_areas">Are you involved in any FLOSS projects? If so in which areas?</a></li>
130 <li>Company & Use case
132 <li><a href="#environments">In which environments do you use Grml?</a></li>
133 <li><a href="#company_name">If you are using Grml in a company, what is the name of the company?</a></li>
134 <li><a href="#company_size">Size of the company</a></li>
135 <li><a href="#company_industry">Industry of the company</a></li>
136 <li><a href="#company_quote">Is there anything you and/or your company would like to say about Grml?</a></li>
140 <li>Questions about Grml
142 <li><a href="#bootmedia">Which boot media are you using for Grml?</a></li>
143 <li><a href="#using_grml_for">Ever used Grml for...</a></li>
144 <li><a href="#creative_solution">What's your most creative solution with Grml?</a></li>
145 <li><a href="#why_using_grml">Why are you using Grml?</a></li>
149 <li>Tools & Programs
151 <li><a href="#using_programs">Which programs did you use at least once?</a></li>
152 <li><a href="#bootoptions">Which bootoptions do you use?</a></li>
153 <li><a href="#windowmanagers">Which windowmanagers do you use on Grml?</a></li>
154 <li><a href="#tools">Which tools would you like to see on Grml?</a></li>
160 <li><a href="#flavours">Which Grml-flavors make sense?</a></li>
161 <li><a href="#dvd">Should we produce a DVD image instead of a CD image?</a></li>
162 <li><a href="#ship_windowmanagers">Should we ship multiple window managers?</a></li>
163 <li><a href="#debian_stable">Do you use Grml packages on Debian-Stable?</a></li>
164 <li><a href="#what_should_be_changed">What else should be changed in Grml?</a></li>
170 <li><a href="#wishlist">Wishlist for improvements on Grml</a></li>
171 <li><a href="#famous_last_words">Did we forget anything? Any famous last words?</a></li>
179 <h3><a name="since_when"></a>Since when have you been using Grml?</h3>
181 <img src="./img/since_when.png" alt="*" />
183 <p>We seem to have a healthy mixture out of longstanding as well as
184 newer users which we consider a good sign to provide high quality
185 together with enough innovation.</p>
187 <h3><a name="stumble"></a>How did you stumble upon Grml?</h3>
189 <img src="./img/stumble.png" alt="*" />
191 <p>Most users come from suggestions by friends or on IRC as well as
192 independent websites. Just about a quarter stumbled upon Grml
193 through official media press. We consider this result as a healthy
194 combination and a proof of the rule how important word-of-mouth
195 recommendations are. Our favourite custom answer: The internet.</p>
197 <h3><a name="located"></a>Where are you located?</h3>
199 <img src="./img/location.png" alt="*" />
201 <p>The first 65 survey results lacked this question and 5% didn't
202 answer this question. As the chart shows we cover all continents but
203 Europe is the place with the largest user base. At the last Grml
204 developer meeting we decided to put effort into providing mirrors
205 outside Europe. Thanks to people providing mirrors rit.edu (New
206 York/US) and ftp.tw.debian.org (Taiwan) our mirror coverage improved
207 a bit already, but our efforts toward improving Grml's coverage
208 outside Europe won't stop.</p>
210 <h3><a name="knowledge"></a>Level of Linux knowledge</h3>
212 <img src="./img/linux_knowledge.png" alt="*" />
214 <p>Most people classify themselves as experts or intermediate. This
215 fits well in our focus. We think we are on track with our user
218 <h3><a name="operating_systems"></a>Which operating systems do you use?</h3>
220 <img src="./img/operating_systems.png" alt="*" />
222 <p>99% of Grml's users use Linux and interestingly BSD got a better
223 result than Mac OS. Amongst the answers in "others" have
224 been Solaris, Haiku, Netware, HPUX, AIX, MS-DOS/FreeDOS, irix, Palm
225 OS5 and Symbian S40, whereas Solaris was the leading answer in
226 "others" with an overall count of 23.</p>
228 <h3><a name="distributions"></a>If you are using Linux, which distributions do you use?</h3>
230 <img src="./img/distributions.png" alt="*" />
232 <p>With a leading 86% our users are Debian users. Nearly half of
233 them also use Ubuntu (or any Ubuntu based derivative) whereas other
234 Linux distributions have a coverage of less than 20% each. The
235 answers "others" included 21x Arch Linux, 10x Grml (hehe!
236 :)), 5x (Free/Open/....)WRT, 3x LFS, 3x Knoppix, 3x Maemo, 2x puppy,
237 2x MEPIS, 2x Mint, 1x DSL, 1x Slacks, 1x Aptosid, 1x Archbang, 1x
238 Quirky, 1x Mandriva, 1x Scientific Linux, 1x Sabayon, 1x OpenBSD
239 (huh? :)), 1x SLiTaz, 1x CrunchBang, 1x AntiX. As a result we can
240 say that most of our users seem to be used to Debian(-based)
243 <h3><a name="project_name"></a>Did you start your own Open Source project?</h3>
245 <p>We got 32 answers, which namely included the following Open
246 source projects: bley, wApua, unburden_home_dir, xpt, Hag
247 (hag-linux.eu.org, Grml derivative or rather a remix BTW, now kinda
248 dead, but I still have some plans), baculafs, undbx, HOG-Man
249 (scientific software), more than 15 ones (the currently most popular
250 being jpdftweak), variety of very small projects, IdyllaOS,
251 timecalc, rffc, bwm-ng, immv, FAI, i3, goldbach, FVWM-Crystal, FDTD,
252 Nagiosms, MirBSD, My personal gooogle, SNPpy, bixfile, ngircd,
253 MikeBrother, HME, gocr, octopus-window-manager, wedabecha, libgpmi /
254 v7us / libmawk / scconfig / libporty and a lot more.</p>
256 <h3><a name="project_areas"></a>Are you involved in any FLOSS projects? If so in which
259 <img src="./img/floss_projects.png" alt="*" />
261 <p>Most of our user are directly involved in development with code
262 62%, documentation 47% and support 44%. Quite some are also involved
263 in packaging (36%) which is no surprise given that Grml is based on
264 Debian and got featured several times on planet.debian.org.</p>
266 <h2>Company & Use case</h2>
268 <h3><a name="environments"></a>In which environments do you use Grml?</h3>
270 <img src="./img/environments_for_grml.png" alt="*" />
272 <p>Nearly all Grml users do use Grml for personal use (94%), whereas
273 53% use Grml in a business environment. 19% of Grml users are using
274 it in an educational environment. This means that most people use
275 Grml for work as well as in their personal environment. Maybe we
276 should provide some examples how to use Grml in different
277 environments (Rescue system for virtualised systems, deployment
280 <h3><a name="company_name"></a>If you are using Grml in a company, what is the name of the
283 <p>We got several names of companies using Grml. Amongst them are
284 established universities as well as well known companies. Thanks for
285 your feedback, we plan to provide the list through a separate
286 webpage in the near future.</p>
288 <h3><a name="company_size"></a>Size of the company</h3>
290 <img src="./img/company_size.png" alt="*" />
292 <h3><a name="company_industry"></a>Industry of the company</h3>
294 <p>No big surprises - most companies are IT related. However there
295 are some non-IT related industries like ecology, healthcare, online
296 gambling and tourism as well. Now we are sure that Grml is used in
297 all different kinds of industries and well accepted.</p>
299 <h3><a name="company_quote"></a>Is there anything you and/or your
300 company would like to say about Grml?</h3>
302 <p>First of all, thanks for all the nice and interesting answers.
303 This was one of the most fun parts to read in the whole survey.</p>
305 <p>Some example quotes:</p>
309 <li>The simplicity of grml often astonishes people around me when
310 I am doing a 1:1 backup using dd or recovering their presumably
311 lost data with testdisk</li>
313 <li>Pure Awesome in tiny ~700 MB :D Seriously, lots of big thanks
314 for maintaing such a great project! Also; kudos for the great
315 naming convention!</li>
317 <li>A real Swiss Army Knife for Linux sysadmins.</li>
319 <li>Best utility Live distro ever.</li>
321 <li>It just fits. Everything is in place and ready to use. From
322 drivers to firmwares (like wifi, fibre channel), programs:
323 ddrhelp, irssi and many others not available elsewhere</li>
325 <li>Reliable, stable and powerful Linux live CD/USB distro. Great for
326 auto write blocking hardware for forensic acquisitions</li>
328 <li>In the past I used knoppix as rescue, since I know grml, I do not
329 need knoppix any more</li>
331 <li>Great work. Thank you so much. Btw, I have just "chsh
332 --shell zsh" because of your great zsh configuration</li>
336 <h2>Questions about Grml</h2>
338 <h3><a name="bootmedia"></a>Which boot media are you using for Grml?</h3>
340 <img src="./img/boot_media.png" alt="*" />
342 <p>CDs are still the most important boot media at 79%, followed by
343 USB with 76%. This means we are on the right track with providing
344 easy to use solutions with grml2usb and dd for our users.
345 Network/PXE setups with 28% and hard-disk installations (18%) are
346 not as common as CDs and USB sticks but still often used. Especially
347 considering the fact that network/PXE environments typically serve
348 larger environments we consider 28% to be an excellent value.</p>
350 <p>Answers filed under "Other" included:</p>
356 <li>ISO on harddisk if the main installation is broken.
357 <strong>Comment:</strong> now directly supported with grml-rescueboot</li>
359 <li>DVD <strong>Comment:</strong> someone using grml2iso</li>
361 <li>cd image in a VM</li>
363 <li>multiboot usb (grml2usb/local.cfg for the rescue)</li>
365 <li>image via toram= (good choice to use debian-live)</li>
367 <li>virtual cd drive. <strong>Comment:</strong> seems to be also
368 used in a virtual environment (IBM RSA, HP iLO,...)</li>
370 <li>iso on hd from grub2. <strong>Comment:</strong> check out grml-rescueboot</li>
372 <li>Remote boot via iso.</li>
374 <li>isofrom (hard disk)</li>
378 <li>.ISO within Virtual Machine</li>
380 <li>Compact Flash</li>
382 <li>Boot from iso</li>
386 <p>We should promote the <a
387 href="http://michael-prokop.at/blog/2011/01/07/booting-iso-images-from-within-grub2/">grml-rescueboot
388 feature</a> more prominently as it seems that there is a market
391 <h3><a name="using_grml_for"></a>Ever used Grml for...</h3>
393 <img src="./img/using_grml_for.png" alt="*" />
395 <p>While we had a look at the answers we immediately noticed that
396 most people (>90%) used Grml for more than one task. This shows
397 that Grml is quite flexible and can be used in several different
398 areas. While the high percentages for Recovery (92%), Hardware
399 diagnostic (77%), Backup (62%) and Network analysis (52%) are no big
400 surprises, the percentages for Forensic (40%), Linux Desktop (29%)
401 and Programming (16%) truly are. This result means that we should
402 keep the Linux Desktop and Programming tasks in mind though the main
403 focus is still on the classic use cases.</p>
405 <h3><a name="creative_solution"></a>What's your most creative solution with Grml?</h3>
407 <p>Ok guys, again. Your answers were really cool and nice, and we
408 are sorry to only give you some quotes but it would take up several
413 <li>My desktop system is basically a USB disk that boots my
414 (remastered) grml (one partition contains the grml & grml64
415 ISOs) and has all user data on another partition (grml-crypt is
416 another neat tool to secure that data). That way, I have my
417 desktop with me everywhere.</li>
419 <li>We set up a grml PXE server in a VM on VSphere 4, because if a
420 client doesn't boot, grml is the first thing we need.</li>
422 <li>PXE-Server which automatically installed Debian via FAI to
423 multiple machines.</li>
425 <li>Grml makes it easy to configure and manage a network of 20+
426 servers: 20+ vmware machines all boot from a single copy of
429 <li>grml64micro, a stripped down remastered version of grml to fit
430 into some few free MB in /boot </li>
432 <li>When I started using it, it was primarily for installing
435 <li>We wrote some auto-install scripts that can non-interactively
436 install certain flavours of Linux on the computer we booted grml
439 <li>I like my phone-home image which boots up with X and opens a
440 tunnel to me. I had nothing to hack since you guys have so many
441 possibilities to modify behaviour. THANKS!</li>
443 <li>automatic boot into an remote application server for idle/unused
446 <li>plug in grml stick, plug in network card, boot it, it will ask
447 you what system you want to install using dialog(1) then it
448 automatically partitions the disk, pulls all the packages and
449 custom software, makes it bootable, configures IP addresses.
452 <li>public surf station (kiosk)</li>
456 <p>Most solutions are related to deployment and rescue. But some are
457 also using it for other purpose like a modified desktop systems.</p>
459 <h3><a name="why_using_grml"></a>Why are you using Grml?</h3>
461 <p>Also just a short overview but it seems that the most important
462 reasons for using Grml are:</p>
466 <li>Based on Debian</li>
468 <li>Command-line interface</li>
470 <li>Ships all necessary command-line tools</li>
476 <p>This means we are on the right track. An excerpt of the
481 <li>Great terminal tools, great choice of X environments (I use
482 dwm and evilwm), very well configured out of the box to discover
483 and give me information on any box or network I boot it from.</li>
485 <li>because it`s based on debian, it early had amd64 support, zsh
486 rocks, in rescue mission its important to have a distri, which
487 supports LVM2 and raid systems oftb, the team reacts very quick on
488 suggestions and answers</li>
490 <li>moved from Knoppix to grml (less X and Office -> more SHELL
491 and Tools) - love debian - love the many, many grml-.... scripts
492 that make it so handy to use - love the names (Funkenzutzler 4 the
495 <li>It's debian-like; I couldn't get debian-live to work for me; It's
496 easy to customize; It contains *all* the packages I needed</li>
498 <li>Meets my basic requirements for a rescue distribution: Debian
499 based, bootable from USB with data persistence, customizable...
500 and it has Emacs!</li>
502 <li>I love GRML. I love what you guys do. I love GRML. I really,
503 really love GRML. This distro has deeply affected my interest in
504 Linux by providing me with out-of-the-box customized professional
505 linux awsomeness. I will never be as good as you guys at anything
506 that you do, I will never be as smart as you guys and I have a
507 fraction of the talent. I could never write a single one of these
508 scripts or customizations.I will never be a professional
509 programmer and I will never be as good at anything as you are at
510 this. But you have allowed me to see what you do and get right in
511 there and do it to, you have allowed me to this extremely advanced
512 stuff that I would never have the chance to access otherwise, let
513 alone even be aware of.</li>
515 <li>1) It boots without X11. 2) Every tool I ever expected to be there,
518 <li>release names :)</li>
520 <li>GRML converted me to zsh. Now I use GRML because of zsh.</li>
522 <li>We tried other live system, of course Knoppix and Kanotix, but Grml
523 just rocks the machines better!</li>
525 <li>Several reasons, in no particular order: * Debian based. *
526 Updated regularly (recent kernel, recent userspace readily
527 available in daily snapshots). * No GUI bloat I wouldn't need
528 anyway. * Excellent zsh config (I now install grml-scripts by
529 default on most of my systems). * Approachable developers. *
530 grml2usb. * grml2ram. * 64bit flavour available.</li>
532 <li>At a first view it seems to have a lot of possibilities in one
533 place - ready to use, The best I ever have seen, I may say:
536 <li>This was the more interesting part to me: "Grml includes a
537 collection of GNU/Linux software especially for system
538 administrators and users of texttools"...</li>
540 <li>Great hardware support and includes all the tools a sysadmin
545 <h2>Tools & Programs</h2>
547 <h3><a name="using_programs"></a>Which programs did you use at least once?</h3>
549 <img src="./img/which_programs.png" alt="*" />
551 <p>Unsurprisingly grml-x is the most used program. Second most used
552 Grml script is grml2usb which is a little bit surprising as it means
553 that for installing Grml to an usb stick it wins over the dd(1)
554 method for many people. grml-network respectively netcardconfig is
555 also expected as you sometimes need to configure your network.
556 grml-live is used more often than grml2hd (which BTW is unsupported)
557 and grml-debootstrap. This means that (at least for our
558 participants) remastering is more common than installing Grml/Debian
559 from within Grml..This clearly shows that Grml can be considered as
560 a framework for generating and maintaining flexible Live
563 <p>Surprisingly MirBSD is used less often than FreeDOS and gPXE.</p>
565 <p>For "other" mostly non Grml-specific tools were
566 mentioned, as well as some not so well known Grml tools like
567 grml-crypt (wrapper for cryptsetup) and grml-chroot (wrapper for
568 chroot, binding /sys, /proc and /dev to the chroot) as well as
569 grml-quickstart. We plan to improve our documentation to cover those
570 not so well known tools.</p>
572 <h3><a name="bootoptions"></a>Which bootoptions do you use?</h3>
574 <img src="./img/bootoptions.png" alt="*" />
576 <p>ssh (start an ssh server while booting), toram (copy the whole cd
577 into ram) and lang (set the language) are the most commonly used
578 bootoptions, covering the common use cases. nofb at 20% was
579 unexpected. Probably there are quite a few machines where our
580 default console configuration (framebuffer) does not work.</p>
582 <p>As one user requested a way to automatically start user-supplied
583 scripts, we want to mention that there's already the
584 "script" bootoption (see <a
585 href="http://git.grml.org/?p=grml-live.git;a=blob_plain;f=templates/GRML/grml-cheatcodes.txt;hb=HEAD">grml-cheatcodes.txt</a>).</p>
587 <p>Surprisingly "forensic" is also quite often mentioned
588 as bootoption. If you're interested in a special product on IT
589 forensics you might want to check out <a
590 href="http://grml-forensic.org/">Grml-Forensic</a>.</p>
592 <h3><a name="windowmanagers"></a>Which windowmanagers do you use on Grml?</h3>
594 <img src="./img/using_window_managers.png" alt="*" />
596 <p>Most common answers were fluxbox / wm-ng (Grml default) and None,
597 right in line with our design target: a proper console. Others
598 mention several small window manager like ratpoison, dwm, i3
601 <p>Because many window managers were mentioned we may reassess the
602 (re)inclusion of some small window managers.</p>
604 <h3><a name="tools"></a>Which tools would you like to see on Grml?</h3>
606 <p>Several tools mentioned here are already included in Grml like
607 for example KVM, others will not be included due to licensing
608 issues. For a complete list of packages shipped by Grml have a look
610 href="http://grml.org/files/release-2010.12/dpkg_get_selections">http://grml.org/files/release-2010.12/dpkg_get_selections
613 <p>We are currently in the process of reviewing all suggested
614 packages and may come up with details at a later date.</p>
616 <h2>Future of Grml</h2>
618 <h3><a name="flavours"></a>Which Grml-flavors make sense?</h3>
620 <img src="./img/grml_flavours.png" alt="*" />
622 <p>Grml-full seems to make sense as well as grml-small. Grml-medium
623 is not quite often used. One interesting suggestion is to combine
624 grml-small and grml-full on one CD. We don't have any plans to ship
625 this, but you can easily do this yourself with grml2iso. Another
626 suggestion was to create a special version for virtualised
627 environments named grml-virt.</p>
629 <p>While grml-medium is not as well accepted as grml-small and
630 grml-full in our community, we will continue to ship grml-medium as
631 it's the perfect and recommended starting point for customized Grml
634 <h3><a name="dvd"></a>Should we produce a DVD image instead of a CD image?</h3>
636 <img src="./img/dvd_images.png" alt="*" />
638 <p>As already stated this question was not that helpful. Nothing to
639 comment besides the graphics and what has been mentioned
642 <h3><a name="ship_windowmanagers"></a>Should we ship multiple window managers?</h3>
644 <img src="./img/window_managers.png" alt="*" />
646 <p>Although the X server isn't used that often on Grml, its users
647 commonly want to use their favourite window manager. As already
648 stated we will reassess the (re)inclusion of some small window
649 managers because of your answers.</p>
651 <h3><a name="debian_stable"></a>Do you use Grml packages on Debian-Stable?</h3>
653 <img src="./img/grml_packages_on_debian.png" alt="*" />
655 <p>Installation of Grml packages on Debian is a rare occurrence,
656 except for grml2usb on Debian stable. Consensus is to not put too
657 much effort into it.</p>
659 <h3><a name="what_should_be_changed"></a>What else should be changed in Grml?</h3>
661 <p>Besides some UX things like better artwork/no links (the browser)
662 after startup in X.org etc. most feedback was quite positive. We got
663 some detailed suggestions like better wireless configuration,
664 automatic selection of the kernel in multiarch environments, and
665 others. We are looking into your requests.</p>
667 <h2>Anything else?</h2>
669 <h3><a name="wishlist"></a>Wishlist for improvements on Grml</h3>
671 <p>We got some really nice ideas like inclusion of support for other
672 boot images in our GRUB environment or multiarch CDs. Better
673 documentation as well as some How-tos was also mentioned several
674 times. Oh and more professionalism for our wallpapers. It seems that
675 at least in one work environment our wallpaper caused some
678 <h3><a name="famous_last_words"></a>Did we forget anything? Any famous last words?</h3>
680 <p>This is again mainly positive things, so just some examples:</p>
684 <li>I hate to disagree with the devs oft stated opinion, but grml
685 is still the best desktop installer to create a usable desktop
686 environment, because everything just works out of the box, and has
687 no distro specific absurdities, like the famous debian forks.</li>
689 <li>Great distro, truley a masterpiece of work.</li>
691 <li>grml is 2 percent Jazz, 98 percent funky stuff ... </li>
693 <li>It is great and it is debian</li>
695 <li>Why don't you get rid of this strange ZSH and switch to the
696 industry standard bash?!?! Haha, j/k :-)</li>
698 <li>Simple: Grml rocks! Thanks for the great work. </li>
700 <li>The answer must be, of course, 42.</li>
702 <li>United as one! Divided by zero!</li>
704 <li>I like the cool distribution names!</li>
706 <li>Thanks guys, I appreciate the work you've put into this
711 <p><a href="#top">Go to the top...</a></p>
715 [% INCLUDE static_bottom.inc %]