Mai 2009 - Grml - lists.mur.at

the linux cookbook
by Josh 28 Okt '09

28 Okt '09

Hi, wow I did not know I could read the linux cookbook online until I did a google search for it and found it online. But here's a problem I need to overcome, and if anyone has already overcome this being blind, can you share how you did it? Ok, so for me to practically use this cookbook, I will need to: *be able to somehow read the book and then go to my computer and follow the directions. so I would need two computers? one to read the book on, and another to have grml Linux on. or *have a braille copy of the Linux cookbook so I therefore only need one computer and can read the braille copy to refer back to. Josh email: jkenn337(a)gmail.com msn: kenn6498ku(a)hotmail.com

3 2

I got Espeakup finally to work
by Hermann 07 Jun '09

07 Jun '09

Hi, just let you know: Espeakup now works in German. I had to pull the latest from GIT, and after compiling I had to type: espeakup -V de or espeakup --default-voice=de Note: You can replace that "de" by any non-English voice. I got the tip from the Speakup list archive. Question: Is it possible to replace the 0.4 by the latest version (0.60)? Second note: the modified characters file is still needed. Hermann --

3 12

The installed GRML boots very slow
by Hermann 02 Jun '09

02 Jun '09

Hi, while checking out your list archive, I found that this was brought up some months ago, but I repeat it: I installed the release candidate of GRML 2008-11 on my desktop machine, and since that I had to observe a slow boot process. My hard drive start spinning and then stops for a long time till it starts moving again. I guess that in the meantime there runs the hardware detection. But why lasts this procedure so long? Below I put the results of: cat /proc/partitions and ll /sys/block major minor #blocks name 8 0 39099375 sda 8 1 15358108 sda1 8 2 1 sda2 8 5 16386268 sda5 8 6 48163 sda6 8 7 7301511 sda7 insgesamt 0 lrwxrwxrwx 1 root root 0 22. Mai 15:15 ram0 -> ../devices/virtual/block/ram0/ lrwxrwxrwx 1 root root 0 22. Mai 15:15 ram1 -> ../devices/virtual/block/ram1/ lrwxrwxrwx 1 root root 0 22. Mai 15:15 ram10 -> ../devices/virtual/block/ram10/ lrwxrwxrwx 1 root root 0 22. Mai 15:15 ram11 -> ../devices/virtual/block/ram11/ lrwxrwxrwx 1 root root 0 22. Mai 15:15 ram12 -> ../devices/virtual/block/ram12/ lrwxrwxrwx 1 root root 0 22. Mai 15:15 ram13 -> ../devices/virtual/block/ram13/ lrwxrwxrwx 1 root root 0 22. Mai 15:15 ram14 -> ../devices/virtual/block/ram14/ lrwxrwxrwx 1 root root 0 22. Mai 15:15 ram15 -> ../devices/virtual/block/ram15/ lrwxrwxrwx 1 root root 0 22. Mai 15:15 ram16 -> ../devices/virtual/block/ram16/ lrwxrwxrwx 1 root root 0 22. Mai 15:15 ram17 -> ../devices/virtual/block/ram17/ lrwxrwxrwx 1 root root 0 22. Mai 15:15 ram18 -> ../devices/virtual/block/ram18/ lrwxrwxrwx 1 root root 0 22. Mai 15:15 ram19 -> ../devices/virtual/block/ram19/ lrwxrwxrwx 1 root root 0 22. Mai 15:15 ram2 -> ../devices/virtual/block/ram2/ lrwxrwxrwx 1 root root 0 22. Mai 15:15 ram20 -> ../devices/virtual/block/ram20/ lrwxrwxrwx 1 root root 0 22. Mai 15:15 ram21 -> ../devices/virtual/block/ram21/ lrwxrwxrwx 1 root root 0 22. Mai 15:15 ram22 -> ../devices/virtual/block/ram22/ lrwxrwxrwx 1 root root 0 22. Mai 15:15 ram23 -> ../devices/virtual/block/ram23/ lrwxrwxrwx 1 root root 0 22. Mai 15:15 ram24 -> ../devices/virtual/block/ram24/ lrwxrwxrwx 1 root root 0 22. Mai 15:15 ram25 -> ../devices/virtual/block/ram25/ lrwxrwxrwx 1 root root 0 22. Mai 15:15 ram26 -> ../devices/virtual/block/ram26/ lrwxrwxrwx 1 root root 0 22. Mai 15:15 ram27 -> ../devices/virtual/block/ram27/ lrwxrwxrwx 1 root root 0 22. Mai 15:15 ram28 -> ../devices/virtual/block/ram28/ lrwxrwxrwx 1 root root 0 22. Mai 15:15 ram29 -> ../devices/virtual/block/ram29/ lrwxrwxrwx 1 root root 0 22. Mai 15:15 ram3 -> ../devices/virtual/block/ram3/ lrwxrwxrwx 1 root root 0 22. Mai 15:15 ram30 -> ../devices/virtual/block/ram30/ lrwxrwxrwx 1 root root 0 22. Mai 15:15 ram31 -> ../devices/virtual/block/ram31/ lrwxrwxrwx 1 root root 0 22. Mai 15:15 ram4 -> ../devices/virtual/block/ram4/ lrwxrwxrwx 1 root root 0 22. Mai 15:15 ram5 -> ../devices/virtual/block/ram5/ lrwxrwxrwx 1 root root 0 22. Mai 15:15 ram6 -> ../devices/virtual/block/ram6/ lrwxrwxrwx 1 root root 0 22. Mai 15:15 ram7 -> ../devices/virtual/block/ram7/ lrwxrwxrwx 1 root root 0 22. Mai 15:15 ram8 -> ../devices/virtual/block/ram8/ lrwxrwxrwx 1 root root 0 22. Mai 15:15 ram9 -> ../devices/virtual/block/ram9/ lrwxrwxrwx 1 root root 0 22. Mai 15:15 sda -> ../devices/pci0000:00/0000:00:07.1/host0/target0:0:0/0:0:0:0/block/sda/ lrwxrwxrwx 1 root root 0 22. Mai 15:15 sr0 -> ../devices/pci0000:00/0000:00:07.1/host1/target1:0:0/1:0:0:0/block/sr0/ lrwxrwxrwx 1 root root 0 22. Mai 15:15 sr1 -> ../devices/pci0000:00/0000:00:07.1/host1/target1:0:1/1:0:1:0/block/sr1/ Anything wrong with that entries? What can I change? I remember that deactivating udev detection is no good idea. Hermann --

2 2

grml2hd udev
by markus 02 Jun '09

02 Jun '09

hi, i have installed the latest grml (schluchtenscheisser). everything was working out of the box and i upgraded (aptitude safe-upgrade) to the latest packages. after a reboot everything was working. after another reboot udev doesn't work anymore (it hangs at populating /dev) and i have to boot with 'noudev' to get it to start. but now i can't access any device like the nw-card, or usb-stick anymore. does anyone know about that problem and how to fix it ? thx, markus.

2 1

Strange messages when performing "modprobe"
by Hermann 02 Jun '09

02 Jun '09

Hi, when I perform a "modprobe", I get the following strange messages: WARNING: All config files need .conf: /etc/modprobe.d/rng-tools, it will be ignored in a future release. WARNING: All config files need .conf: /etc/modprobe.d/blacklist-capiutils, it will be ignored in a future release. WARNING: All config files need .conf: /etc/modprobe.d/irda-utils, it will be ignored in a future release. WARNING: All config files need .conf: /etc/modprobe.d/hostap-utils, it will be ignored in a future release. WARNING: All config files need .conf: /etc/modprobe.d/alsa-base-blacklist, it will be ignored in a future release. WARNING: All config files need .conf: /etc/modprobe.d/alsa-base, it will be ignored in a future release. WARNING: All config files need .conf: /etc/modprobe.d/kqemu, it will be ignored in a future release. WARNING: All config files need .conf: /etc/modprobe.d/linux-sound-base_noOSS, it will be ignored in a future release. WARNING: All config files need .conf: /etc/modprobe.d/sl-modem-daemon.modutils, it will be ignored in a future release. WARNING: All config files need .conf: /etc/modprobe.d/madwifi, it will be ignored in a future release. What does this mean? Hermann

2 1

Why does GRML mix up the stable and teh unstable branche in apt?
by Hermann 02 Jun '09

02 Jun '09

Hi, a few weeks ago, I installed Gnome on my GRML 2008-11. Since Gnome shipps a lot of updates, I got a lot of stuff from the unstable branche of the repo. This results in screwing up my system, especially Gnome. So I commented out the unstable branche and removed comment chars from the testing branche; the stability was much better. But due to the lack of performance I finally got rid of Gnome. But the question stays: Why is stable and unstable mixed up on GRML, instead of including the testing branche? With one exception, this mixing caused no problem on the text console. Hermann --

2 1

Speakup and non-ascii characters
by Michael Whapples 25 Mai '09

25 Mai '09

Hello, This is in response to an email by Hermann, I am not doing it as a reply as I get messages as a digest and lost the original message. First thing to note is that speakup as far as I know has its own character table which it uses for pronouncing characters when saying individual characters (eg. spelling, cursoring over characters, etc). This table can be found in /sys/modules/speakup/parameters/characters and so can be edited there. Speakup by default lists characters up to value 255, although values beyond 127 depend on the encoding used (eg. latin1, utf-8, etc) for the actual definition. As far as I know espeakup doesn't modify this table, speechd-up can replace the tables or leave them alone (there is an option for speechd-up to specify this). One way to fix this is to create a script to modify the table or copy a new table into /sys/modules/speakup/parameters/characters and to do this on start up. Does this help? Michael Whapples

2 8

GRML does not boot on all machines since version 2008-11
by Hermann 22 Mai '09

22 Mai '09

Hi, since version 2008-11 I cannot boot the live CD anymore on one of my machines - my desktop computer - a PC bought at the German computer store Vobis. They use noname components, but the computer contains an AMD Duron processor of 1 Ghz and has 256 MB RAM. All former GRML-Versions, including the 2008-11 release candidate did boot well. On my notebook - Acer 1600, Intel processor 2,7 Ghz, 512 MB RAM, I can boot every GRML CD. After taking a long time, the CD seems to hang, and because I'm blind, I cannot check out what is written on the screen. Is there a way to redirect the output, for example to a file on a floppy drive? And, most important, waht is the reason for this? I use the GRML CDs to backup and restore my systems via partimage. Any hints? Hermann --

2 2

Speakup doesn't speak German correctly and is only partial usable
by Hermann 22 Mai '09

22 Mai '09

Hi, perhaps this is better written to the Speakup list, but I'll try to put this here: When using Speakup together with Espeak either via Speech-dispatcher with speechd-up, or together with Espeakup, The speech does not recognize all characters correctly: Most annoying are the German umlauts, which are not recognized at all by Espeakup and only partially by speechd-up. In the latter case I can hear them when typing and continuously reading, but they are pronounced wrong when deleting them and when moving char by char via the cursor-left-right keys. For Example: "ü" is "power" and "ä" is "sigma". Moreover: An "a" is spelled as "aik", and all punctuation chars and numbers are in English. Most unusable is Espeakup, where it is impossible to read a German text. What is the experience of other non-English Speakup users? Note: It is not an Espeak problem, because when I use it with Speech-dispatcher and the speech functions, provided by the screen readers Brltty and Suse-Blinux, they work well. Hermann --

1 0

Release Candidate 1 of grml 2009.05 available
by Michael Prokop 21 Mai '09

21 Mai '09

Hi! We have new release candidates: the first release candidate of version 2009.05 codename "Lackdose-Allergie" is available! Take a look at the release announcement for details about all the nifty new features: http://grml.org/changelogs/README-grml-2009.05/ As usual we have different flavours available: the 32bit versions grml, grml-medium and grml-small as well as the 64bit versions grml64, grml64-medium and grml64-small. Please test the ISOs and all the stuff you usually need so we can provide rocking stable releases soon. Download the ISOs from the devel directory of the mirrors listed at http://grml.org/download/ Happy hacking and have fun with grml! regards, -mika- -- http://grml.org/ # Linux for texttool-users and sysadmins http://wiki.grml.org/ # share your knowledge http://grml.supersized.org/ # the grml development weblog #grml @ irc.freenode.org # meet us on irc

1 0