On Mon, Oct 12, 2009 at 8:51 PM, Ralf Mardorf <[email protected]> wrote: > Hi :) > <SNIP> > I'm a little bit confused about the separation between user and root on the > Ubuntu based 64 Studio. Does anybody know how I can launch an application as > user by my shell script, even if the script was started as root? > This is needed, because when running the script by "sudo sh obsession0.5" a > jack_snapshot installer will appear and I would like to have an option to > browse to the homepage of jack_snapshot, but by doing this as user and not > as root. > hi,
It would be better to just list jack_snapshot as a dependency, requiring users to install it separately before using the script. Reasons: Most users won't want - or do not have the permissions - to run a script as a root. Since Installation of dependencies only needs to be done once while script is run often it is good habit to separate installation from applications. <SNIP> > Does anybody know how to get the information about ALSA and or JACK MIDI > connections? for Alsa: aconnect -i and aconnect -o for Jack (audio and Jack-Midi): jack_lsp Some more general thoughts: The concept of storing and restoring a session by a script has its limitations: Well written (most) applications can be started from the command line with options that allow to exactly restore a prior state. IMHO running applications cannot be queried about all those options via command line. So restoring a session by a script is perfectly possible. In terms of storing a session, a script would be rather weak. What a script could do is save a template script from a set of interconnected applications. The user then could manually fix and extend that template and use it as a startup script. Just an idea that came to me. best, d _______________________________________________ 64studio-users mailing list [email protected] http://lists.64studio.com/mailman/listinfo/64studio-users
