the linix audio circus

What have I overjumped, to just understand rail way station here?

If I could one day identify this I will be glad:





I put these screenshots as impressions of this odyssey:











What you not say?“ Do not loose your time. … This program is not for anybody.“ Says he.




It seems by all that:  is important to me.

and     ** HOW TO GET STARTED WITH MIDI COMPOSITION ON ROSEGARDEN **, together with five, six others. – But:

the thing is: when I have got rosegarden fired up, the soundcard is out of use for the rest applications. Right? So I have to run on another computer with live cd these videos. Hopefully they have any „codec“ swindle. Have they? Ok: I hear the video and I see it on the other computers live cd.  I go for it…

I just want to try some guaguanco with some montunos. Pardon tumbao. That is what I basically want, hope that there is some a) template for it and b) tutorial through GUI enough. Maybe time for a new post, too.

linked text

Question of the post: How the hell shall I get order in this zoo? Can anybody help me?



A Alsa-Salsa-Project hello worlds and first steps

On composing with rosegarden, it is to say that each time I fire it up, it needs a hassle of 1 hour to have it spit out a tone at Ubuntu 14.04 LTS. Thanks. And I am handling it now over a year.  Do not know at which time the system denies service for ever. I mean that drastic is the situation. (can be seen commercialisation self crippling very corrupt and modern effect of big business entering in free software , why not? That explains why we need brute force methods: kill the processes from the kernel process lists with a root account for regular usage, who responds to this situation? Not the user, at least. One can read this as always as odyssey as demonstration of hindrance. One comes to the conclusion, that the these systems of software offering be it the vm-case (upper post on „easy vms“, be it rosegarden, pretend that they do not care the casual user a demo fireup at first usage and anyway „hello world“ feature? One would consider a such a casual user contact as a gros offence.
So: There is a grossly the user offending practice, pleasing commercialisation, free software interests anyway, is not it?
Grossly user offending is something I would condemn and undermine. One should fire regular stress tests at this bug, I find. Anyway, at least, I find, that with finding this phenomenon happen in other parts of the tool chain of various softwares, that does not excuse from the accuse of having user mistreat happen using their tools. So one does not deem, if any free software people get defensiv too soon, right? I hope this question gets a soon solution, that what I can say. Why, hell, their is no „hello world“ of your work available? Still not, is that not getting similar keeping them away from the user? Yes? Yes? They say the do not think in the use case of their casual usage so much, but in those of there customers. That is that, what they are saying and that by no means crosses the line free software rights. But then after a years off servicing they take the form of crippled user interface for their -casual- users. It may be arguable, that this is the case here, but I soon would argue that. It seems over more that one should better have intervened already years earlier. I do by no means want a hall of shame for this kind of cases, but a bug tracker. I gonna stuff that in their bug tracker, lets see, how they notice it.


Have fun!)

Anyway, I cycle at it:

This is the script supposed to be working:


qjackctl -s
timidity -iA -Oj -B2,8
Result: Sound

Test1 shutdown from Test0

[2] Fertig qjackctl -s
[4]+ Fertig rosegarden

root~# killall rosegarden; killall qjackctl; kill -9 `ps aux|grep „timi\|jack“|cut -c10-15`;aplay /usr/share/sounds/alsa/Front_Center.wav

Result: clean and default sound hearable again.

Test2 after Test1 run Test 0

qjackctl -s&

sleep 3
timidity -iA -Oj -B2,8&

sleep 3  # I ask everybody which user could step over that easily about this usage barrier?


#open lasst file with, play, no sound, go to Studio/MidiMixer, there play flipper a little with the option until Sound appears at you ears.

result: all measures fail

Test3 after Test1

state of the art: qjackctl -s& sleep 3; timidity -iA -Oj -B2,8& sleep 3; rosegarden –nosplash .local/share/rosegarden/examples/bogus-surf-jam.rg &

press play in gui
Result: Sound

Test4: Give me immediate Sound after rosegarden fire! up

to be done
How can help me doing this Test 4.
linked text


time budget for this project is over, could be a year or so.

my personal time budget for this project is over and I must push achieving the target on the long bank so to say, which could be a year or so.
These are the threads about the current state of acknowledge about realize such thing.
and here
and here

For somebody accidentally reaches that aim in the meanwhile (on top of it or no), please let me know.
If so, good luck and have fun.


Status quo: locked out after preseed

(10.6.16: hint before the beginning found a solution for it (; see: post „the preseed solution then“)

Problem situation of a first project:

Result: After the below preseeding I do not find a system, where I find the guest controlled by a ssh connection, like I would expect that

This is the preseed.cfg

This is the command line:

virt-install –connect=qemu:///system –location=\-i386 –initrd-inject=$HOME/Downloads/preseed.cfg –extra-args=“auto“ –name virtdebstable3 –ram=512 –disk=pool=default,size=5,format=qcow2,bus=virtio –network=bridge:virbr0 –hvm –accelerate –vnc &

This is the ip-network on the host I found after install  (I do not remember by who it was configured):

# ifconfig |grep -v „inet6\|UP\|RX\|TX\|Kol“
eth0 Link encap:Ethernet Hardware Adresse 18:03:73:87:af:2e

lo Link encap:Lokale Schleife
inet Adresse: Maske:

virbr0 Link encap:Ethernet Hardware Adresse fe:54:00:66:47:6c
inet Adresse: Bcast: Maske:

vnet0 Link encap:Ethernet Hardware Adresse fe:54:00:ff:c4:4f

vnet1 Link encap:Ethernet Hardware Adresse fe:54:00:66:47:6c

vnet2 Link encap:Ethernet Hardware Adresse fe:54:00:bb:82:ea

wlan0 Link encap:Ethernet Hardware Adresse ac:72:89:84:5d:c3
inet Adresse: Bcast: Maske:

This is what guest says:


try running cl without inject=$HOME/Downloads/preseed.cfg:

Network is ok,, Setting PermitRootLogin to Yes

„interface standard between virt-install and d-i preseeding for the present use case?“

Questions: „Is there a requirements interface standard between virt-install and d-i preseeding for the present use case?“

-why is there no  existing, proper preseeding script, if there is even a  –initrd-inject built in virt-install?

Test 2: (failed, same as Test0)

d-i netcfg/dhcp_options select Retry network autoconfiguration

d-i netcfg/choose_interface select eth0

Result: same as Test 0.

Test 3:(failed, same as Test0)

virt-install –connect=qemu:///system –location=\-i386 –initrd-inject=$HOME/Downloads/preseed.cfg –extra-args=“netcfg/get_ipaddress= netcfg/get_netmask= netcfg/get_gateway= netcfg/get_nameservers= netcfg/disable_dhcp=true“ –name virtdebstable6 –ram=512 –disk=pool=default,size=5,format=qcow2,bus=virtio –network network=default –hvm –accelerate –vnc


Google: virtual network libvirt qemu gives:

This is 25 Chapter, overkill, but one may state, that the button „ssh easy image“ is missing definitely.      Do not understand that. It does not help me? But I am googling right now: „libvirt qemu ssh“

Google: „–initrd-inject“ virt-install preseed         –extra-args auto=true hostname=${OS} domain= url= text   MY TECH EXPERIENCES: commented link lists of others with their odyssey experiences on preceeding    this is about : Love your enemies? even: to learn loving enemies. Aha?    We couldn’t find any code matching ‚preseed‘

c.add_valid(–location %(TREEDIR)s –initrd-inject virt-install –extra-args ks=file:/virt-install) # initrd-inject

So there is a file somewhere with name impossible to find: „virt-install“     at September 18th, 2009. „I don’t want to set an IP address in the file as it’s going to be used to build lots of machines“

--extra-args="auto=true interface=eth0 hostname=${NAME} netcfg/get_ipaddress= netcfg/get_netmask= netcfg/get_gateway= netcfg/get_nameservers= netcfg/disable_dhcp=true url=http://webserver/preseed.cfg"

d-i netcfg/choose_interface select eth0
d-i netcfg/disable_dhcp boolean true
d-i netcfg/dhcp_options select Configure network manually
d-i netcfg/confirm_static boolean true

This he got „libvirt virtual networking“ setup?

Debug methods, preseed methods:

  • default: rudimentary trial and error, well it is comic to ask for best practice if the governing practice hardly can not be worse, one might smile with stoicism:
    • you take a template from the internet, official or not official,
    • each run take an hour
    • you add entries for questions or any other misbehavior where it fails until you got the result aimed for, each test needs hours. This is health threatening development practice, as a test run should long milliseconds: He says it: do not know exactly at which minute. So one can hold fast that all these oudeises around have not hit that ground: that the user is probably set out to some unbearable truth, something that is critical to change and claimable to find a way for. It is better oudeis‘ duty to claim that – put it to the feature request list …
  • well, found
### Preseeding other packages
# Depending on what software you choose to install, or if things go wrong
# during the installation process, it's possible that other questions may
# be asked. You can preseed those too, of course. To get a list of every
# possible question that could be asked during an install, do an
# installation, and then run these commands:
#   debconf-get-selections --installer > file
#   debconf-get-selections >> file

-so one can guess on the upcoming questions and their answer

-on top of present non preceeding but correct os installation, one can look up promising preseed options

debconf-get-selections –install>1;debconf-get-selections >>1; cat 1|grep -v exim4 |grep -A2 „eth0\|netcfg\|hostname“|wc
0 0 0

root@debian:~# debconf-get-selections –install>1;debconf-get-selections >>1; cat 1|grep -v exim4 |grep „eth0\|netcfg\|hostname\|d-i“|grep -v „keyboard\|language\|country\|language“|wc
0 0 0

in other words: we will find anything but network configuration template within these thousand lines.

debconf-get-selections –install>1;debconf-get-selections >>1; cat 1|wc
770 10102 109616

Aim: What ever iptables hack I choose, I want to have straight ssh key access from the host.

Pathes of preseeding

Naming of the Testcases:

So if one wants to measure the space of preseeding use cases theoretically:  3 * 3 *3*15*7

octave:1> 3 * 3 *3*15*7
ans = 2835

That is the chance to be misunderstood (as a help seeking user and as someone asking for working demos), because unprecise determination in this world of creationg is extrem. So we are extra-careful. Then wie need to proove that a maintainer’s demoscript is working and btw. keep it in the Testsuite. For example

a testfunction is then programmatically named




These are the use cases I figured out:

-case Environment: physical Hardware (hw), qemu, chroot( 3)
-case: Ubuntu/Debian/Linux (3)
-case: Guest:Ubuntu/Debian/Linux(3)
-case: Tool vor creation: one of the Fifteen
-case methods (about 7):
Debian methods: create the Boot-Medium  (hw) (These are two enduring processes: 1. creation 2.installation AUS DEM NETZWERK HOCHFAHREN

PXE (?)configuration for the boot server:/tftpboot/pxelinux.cfg/default

Preseed-Datei nach /media/usbdisk/preseed.cfg EIN CD-ROM-ABBILD ERSTELLEN

debian-cd/README.. (hw: complicated?)

  extended Ubuntu methods (who many?)

  virt-install methods:  (who many?)

-(inject from path and netinstall)

working Demo:

virt-install –connect=qemu:///system –location=\-i386 –initrd-inject=Downloads/preseed.cfg –extra-args=“auto“ –name d-i –ram=512 –disk=pool=default,size=5,format=qcow2,bus=virtio

-(other use cases, which not, which are left?)

Commented Link List;a=summary who is packer?

BabelBox: automated DebianInstaller testing and demo machine


BabelBox is a system designed to demonstrate the automation (bingo) capabilities of the Debian Installer. It also shows the high number and the quality of translations available for the installer. It is well suited for a live demo  (bingo)on a booth in an expo or any other event.

Todo: -issue a feature request:foolproof, out of box, quick preseed testing, feature: Test_whole_debian_family_playing_check_against_each_other

-install on test machine with virt qemu cl, running a hello world to run a guest in a guest, good Idea? cpmletiong state, stale: no ip connection with host.

-BabelBox: a lot installation, a lot installation planning.. Automate installs with preseed 8 automation usage cases as Howtos BabelBox, web-if for sources, preseed 10 years old  Installation report template  so, this is the official uptodate developement repro git hub of debian? Ok . This webif does not of to look up the author and date per file as known from github, one should use local git.      here preceeding developement takes place as well, at least perl test suite for preseeding   the zoo

three preconfiguration methods=(initrd-preseed file-preseed network-preseed)

8*4*4  Installation methods=

(Boot Udebs ? Base system Tasks)*(CD network harddisk USB CDimage)(netboot mini.iso businesscard CD netinst CD full CD/DVD hd-media)

The five stages with its components with the three preseedings between.

Here you got the vocabulary, do you know all? This is the big picture. And surely you can demo test none of them.

About the Is-Situation, about users‘ annoyed, 10 years lasting and now situation; a frequent opinion to be found about the historic situation of availability of the functionality. It is the accusation against the development of preseeding as a whole, limiting the user sensibly and have him kept away from the functionality as hopelessly remorseless as effectively permanent.-  Worth to be discussed in how far this gets true.  Hardly to imaging to find a setting in which to discuss it governed by rationality – probably! Does that say, that these „admins-developers“ keep it messy, not to loose the jobs? If so then hostile intention shall be considered. And: Debian is by no means the only tool for donating confusion.  qemu, lib-virt live in the same boat assuming any such regime of desinformation. In a broader view I have not considered, if security concerns could be affected or not.  I at for moral objections can perceive no impiousness around heading for a world of „easy images“ – up to now .  I rather should consider „racket influence“ instead, some „brain wash“ among the people concerned, maintaining them users in odyssey mode while leaving time at it. The situation is bizarr.  They think in everything but not in maintaining a „easy image“ solution; here is where doubts come up. If one needs to admit, that an „easy image“ solution is not simply possible, this equivalents to „we have not even a „hello world“ of our software.  As the software than appears rather a big „hey“ stack of scripts of historic staff, one should head for a completely new design and rewrite. And to a discussion about it. For my problems at the stage I am writing this, I believe: having not a decent IP connection to the guest is an qemu issue .. Good by and good Luck Debian, Debian-Installer by now. (:

Yes, and one could check ouf babelbox, but therefore it is necessary to learn packer. Packer?

On the other hand, thinking on a campaign  qemu-buro-dpkg comes in. Why not ask among  the 240 coderd and contributors of – for example nowadays – packer, to provide a  „helloworld easy image“ for qemu-buro? Is it not easier on base of this analysis, to just contribute an „hello world“ and then return to your code work of your presumed business world around images without? I want to reasonably petition to contribute code on the debian-boot mailing list. Thanks in advance.   another newer unofficial block including the below, but where is the explication to hello world a guest?

d-i preseed/late_command string \ in-target wget -O /root/; \ in-target /bin/bash /root/ I could not understand otherwise than another promising „we wont hello world for you“ show: „QEMU, Virtualbox, and VMware builders“

lightweight, portable, and command-line driven. This makes it the perfect tool to put in the middle of your continuous delivery pipeline.   says „JavaScript“ is a trademark of Oracle Corporation.[35]“ 

Why do they torture users with json format, is their anything to learn from it? Before using me, you should should put a file .json on your computer? This what you call command line usage? (No?) Jason? Was not the speech from him, when oudeis went to Kirke?



Story zum Projekt qemu-buro.dpkg



also hier soll die Story zum Projekt qemu-buro.dpkg plaziert werden, so eine Story gilt ja gemeinhin als wichtiger Bestandteil von Projekten.

English: Nothing. This is the story to the project qemu-buro.dpkg „ease around images for everybody“  to be found on github, see link below. Read the english snippets in the faq and the readme. Help writing the Testfunction, provide working testcase demos of your programm  or help advice further planning! Have fun!


Es war ein Tag wie jeder andere, als ich die turnusmäßigen Arbeiten zur Büropflege startet. Neuinstallation stand auf dem Programm, gleich zweimal. Also gehe ich artig ins Forum mit dem Namen „vor der Installation von Ubuntu“. Ich suche nach Möglichkeiten die Arbeiten gar nicht oder menschenfreundlicher zu machen, statt händisch. Das misslang wieder mal. Um mit diesen lebenslangen Problem umzugehen, beschloss ich andere Geschütze aufzufahren. Und so endete der Tag dann:

git push —force -u origin master

Password for ‚‘:
Counting objects: 7, done.
Delta compression using up to 4 threads.
Compressing objects: 100% (6/6), done.
Writing objects: 100% (6/6), 3.47 KiB | 0 bytes/s, done.
Total 6 (delta 0), reused 0 (delta 0)
+ 506bbd7…c3a1125 master -> master (forced update)

qemuburo$ python –m unittest Testqemuburo.qemuburoTestCase.test_pre_and_post_instalaion_tests_from_qemu_generation_to_ready_use_image
Ran 1 test in 0.017s


Learning by doing and learning by testing and programming test driven.

mit template scripts, Readmedatei, fertig ist die Automationsstrecke für jedermann.

So wie erledige ich das jetzt? Nächste Frage.


-Alleinstellungsmerkmal. Tatsächlich. Hat noch keiner gemacht außer mir.

-Also jetzt geht es los, mit welchen tools und mit welchen tool chains ich die Strecke automatisieren könnte:

1Sagt einer qemu-ua,
-quatsch pexpect,
-der zweite quatsch uvtools,
-der dritte lxd,
-presseeding in verschiedenen Formen,

-Kickstart/Kickseed Ubuntu?
10 aqemu
15 babelbox

-keins von denen?

– Phänomenfall: öffentliches Geheimnis. Gegenwind, so fühlt es sich an.

– Situation: trotzdem viel freie software Aktivität in dem Bereich: Es wäre in der Tat einfacher jemand erfahrenes codet eben die vorgestellten Testfunktion(en) auf git-hub oder hilft bei der Planung.

– Der Deal: Nichts desto weniger werde ich in Zukunft noch öfters hier cyclen und time budget slices hier verbrauchen. Und so liegt, die Projektbearbeitung auf der langen Bank. github wird bekannt gegeben. Nachgefragt ist: tool-chain Planungsbeiträge und, klar, Code.  Ok?

Das ist also der Like zum Projekt:


-klassisch Spenden? Kenn ich nicht. Fundraising. Steht irgendwo auf dem Zettel. …

-Verkauf von was?

Wie bekommt ein Hartz4er die best-startfähige Büroumgebungkurse, dezent anbieten, mit „unserm“ tool kit, aber natürlich muss gesorgt sein, dass die Teilnehmer freiwillig da sind. Ich denke da ist Markt dann. Sonst wo nicht so vielleicht. Einigermaßen schwer einzuschätzen, wie sich das entwickelt in Zukunft und ob das Verkauftsszenario eintreten kann? Fördergelder-Geschäfte? Geld stinkt nicht oder? Aber ja: irgendwie begründete Trainingskurse um die vertriebenen Produkte zu nutzen. Es ist jedenfalls nicht ausgeschlossen, dass auch Geld in das Projekt fließt, befinde ich und könnte mir sogar vorstellen, dass das funktioniert.


Zu allen anderen Fragen,die FAQ unten und zu das Readme für Featureliste.
Hier einige Zitate wie ich versucht das Tool zu erklären als FAQ:
-Hey, ppl, it is not difficult rather straight forward.
-Initial question: Where can I find any help for planing my project developing qemu-buro.dpkg? “
-straight forword: because you ask: What has the typical user to do to use his vm? Why is that that complicated and not yet automated, if it is for everyday use. So by time lets go and figure out which parts are not automated, find a solution and package it. That is my bet.
-qcow2 images for idiots, why not?
-Well it is to say, one person understood me in english, but everybody in german saw no sense in it.
-it is the matter itsself that causes pain. The matter of any idiot having a valuable virtual system on just ok-clicking. Thats my aim I point directly to blind spot. Maybe I am wrong, up to now this is my bet.
-wanted to get a minimal qemu image which I can setup by ssh, lets say, apt-get install icewm. can xxx do _this?
-bislang hat vmware noch einen hohe Anteil an der Nutzerschaft. Aber nach einiger Zeit kommt freie Software und erobert den Markt.
-der user soll auf den Fingerschnipp selbst und fertig konfigurierte qwow2 images bekommen.
-das gibt es wohl noch nicht.
-Es ist schon geprüft, dass das wahrscheinlich ein Alleinstellungsmerkmal ist.
-sie sollen fertig zum Gebrauch sein, ja aber auch selbst konfiguriert.
-der user stellt sich das Image her, aber er macht es auf Knopfdruck
-With cloud-localds. Stop thinking about rolling your own images 🙂

Of course, you can do what you want.
But this philosophy is that you don’t prepare your own images. Instead you use the same official image everywhere, and it sets itself up as you wish on boot.
Using cloud-init.
And you give it your ssh key on boot via one of the available mechanisms.
On EC2, that is the metadata service, etc.
For local qemu, you can use a „config drive“ which cloud-localds can prepare for you.
uvtool does this automatically for you for local use.
Then you don’t have to maintain your own images, which inevitably don’t get updated with security updates.

wanna issue a Featurerequest/Bugreport qemu buro? First think. Preseeding code have not been touched from among 7 Billions 10 years long.  Obviously the world is that much desinterested in automated installers, that no features are developed. This means bug have always good chance to beat stability (of availability of product for customer/user). So take the hat with long term mindset on it, file it, keep an eye on it and by the time come with your own solution of it, So issue a pull request on git-hub. Each bug fix molds our code. That is simply the principle of test driven development.

Thereby you are facing Debian install tests.  You could btw help debian with install report, see link list.