- Grml - lists.mur.at

Creating a bootable DVD using grml and grml64
by Ernesto Domato 09 Jun '09

09 Jun '09

Hi, I'd like to create a bootable DVD from the ISOs of grml and grml64 so I can boot whichever of the two flavors or even aggregate the rest of the ISOs to the DVD (small and medium for i585 and amd64). I tried to use grml2usb doing this: 1) dd if=/dev/zero of=dvd.iso bs=1M count=2000 2) losetup /dev/loop1 dvd.iso 3) echo -en "n\np\n1\n\n\nt\n6\na\n1\n w\n" | fdisk /dev/loop1 4) mkfs.vfat /dev/loop1 5) grml2usb grml_2009.05.iso grml64_2009.05.iso /dev/loop1 But it didn't work. There's seems to be some problem when installing the bootloader. What did you think?, Is it possible to do what I want?, should I use grml-live to create custom ISOs?. Greettings and excuse for my english but it's now my native language. Ernesto PS: if it can be done, I'd like to make a CD with for example grml-medium and grml64-medium on it too

2 4

Re: [Grml] Accessibility stuff: was: Re: I got Espeakup finally to work
by Michael Whapples 08 Jun '09

08 Jun '09

On 08/06/09 09:35, Hermann wrote: > On 08.06.2009 10:12, Michael Whapples wrote: > [...] > >> In most other cases (eg. you mention brltty) >> there are alternatives (eg. brltty I thought can use espeak directly). > > No it can't. You have to use SD in order to use Espeak. So SD is > important for non-English speaking users. > I stand corrected, I just assumed as it supports, flite, festival, swift, viavoice, etc directly that espeak might be, no the docs don't mention espeak support. >> I >> would like to accept speech-dispatcher as the obvious choice for speech >> output but unfortunately its problem with crashing from time to time (I >> think it was you Hermann who said it has something to do with its ALSA >> support) makes me personally want to back away from it. > > Yes, but unfortunately the SD team cannot find what causes this. It > does not appear on all machines, so it is difficault to figure out > what's going on. > Moreover: It seems to be an Espeak problem, since other synts don't > crash at all or very seldom (for example Voxin). > I am sure I have had voxin crash on me when using speech-dispatcher. Anyway it seems like it will be a hard bug to track down. >> Although I have >> my personal feelings on speech-dispatcher I accept there are reasons to >> use it so would say it should stay if possible. >> > I agree, but in addition I would prefere to have drivers for synths > that communicate directly with the apps, such as Espeakup. > But perhaps that's what I'm familiar from Windows. Hardcore Linux > users seem to prefer server solutions. I'm not saying don't have direct drivers like espeakup, particularly at the moment when speech-dispatcher still has some bugs which impact on useability. I just consider speech-dispatcher should be treated like SAPI is on windows. I thought that on windows when an application added speech output they tending to add SAPI support first before adding direct drivers for the synths. I also have to say although server processes can be useful at times, I think there are times it seems to go too far on linux. Michael Whapples > Hermann

1 0

Re: [Grml] Accessibility stuff: was: Re: I got Espeakup finally to work
by Michael Whapples 08 Jun '09

08 Jun '09

I would agree. As far as I know for self voicing emacs there's either emacspeak which requires either a hardware synth or viavoice which is commercial, or speechd-el which can use speech-dispatcher, so speechd-el and speech-dispatcher seems to be the best free solution for software self voicing of emacs. In most other cases (eg. you mention brltty) there are alternatives (eg. brltty I thought can use espeak directly). I would like to accept speech-dispatcher as the obvious choice for speech output but unfortunately its problem with crashing from time to time (I think it was you Hermann who said it has something to do with its ALSA support) makes me personally want to back away from it. Although I have my personal feelings on speech-dispatcher I accept there are reasons to use it so would say it should stay if possible. Michael Whapples On 07/06/09 21:41, Hermann wrote: > Just one brief remark regarding Speech-dispatcher: > It should stay on GRML, because it is used as speech output by other > a11y apps, above all Brltty. It is also supported by other screen > readers like Suse-Blinux. > But besides that, Espeakup is good stuff. > Hermann > (No need for quoting in this case, I think).

1 0

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

Still no start of the CD on my desktop machine
by Hermann 02 Jun '09

02 Jun '09

Hi, just downloaded and burned the latest GRML CD, and I had to notice that I still cannot start it on my desktop machine like all the others since 2008-11. So has anything changed regarding this bug? Hermann

2 2

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

grml 2009.05 released
by Michael Prokop 01 Jun '09

01 Jun '09

Hi grml fans, on behalf of the grml team, I'm proud to be able to announce a new stable release: grml 2009.05 with codename Lackdose-Allergie, available in flavours grml, grml-medium and grml-small and all of them as 32bit and 64bit version has been released. The official release announcements providing all the relevant news are available at: grml => http://grml.org/changelogs/README-grml-2009.05/ grml64 => http://grml.org/changelogs/README-grml64-2009.05/ grml-medium => http://grml.org/changelogs/README-grml-medium-2009.05/ grml64-medium => http://grml.org/changelogs/README-grml64-medium-2009.05/ grml-small => http://grml.org/changelogs/README-grml-small-2009.05/ grml64-small => http://grml.org/changelogs/README-grml64-small-2009.05/ Issues regarding the releases can be found in the grml-wiki at: grml => http://wiki.grml.org/doku.php?id=grml_2009.05 grml64 => http://wiki.grml.org/doku.php?id=grml64_2009.05 grml-medium => http://wiki.grml.org/doku.php?id=grml-medium_2009.05 grml64-medium => http://wiki.grml.org/doku.php?id=grml64-medium_2009.05 grml-small => http://wiki.grml.org/doku.php?id=grml-small_2009.05 grml64-small => http://wiki.grml.org/doku.php?id=grml64-small_2009.05 If you're interested in the main changes between rc1 of 2009.05 and the stable release: http://grml.supersized.org/archives/319-changes-between-grml-2009.05-rc1-an… As usual you can get the ISO(s) via bittorrent, http and/or ftp from the mirrors listed at: http://grml.org/download/ Have fun and enjoy the new release! As usual your feedback is highly appreciated. 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