and https://www.youtube.com/watch?v=0-X6_q1iRzc ** 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.

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.

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: https://www.youtube.com/watch?v=2lrRix3PM4k 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

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

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.

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 impiousnessaround 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.

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

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!

FAQ

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 🙂
rolling?

Creating
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.