On Sat, 5 Sep 2015 08:51:09 +0200, Ralf Mardorf wrote: >On Fri, 4 Sep 2015 19:52:07 -0700 (PDT), Len Ovens wrote: >>On Fri, 4 Sep 2015, Kaj Ailomaa wrote: >> >>> The gui will be important for the largest amount of users, so I can >>> not see -controls without one. >>> But, of course, we could have command line options as well, or have >>> a separate command line tool with access to the same functions as >>> the -controls application. >> >>The commandline option is already available. At least for those who >>wish to learn. Those who want to learn more about their system will >>likely customize it to their wants with their own scripts. The GUI is >>for those who want to start creating from first boot. > >You can provide both, the easy experience in combination with learning >by doing. The mechanism should be something similar to visudo, quasi >viubuntustudio-control, then add a launcher and an explanation to the >default file. > >Instead of viubuntustudio-control I used pluma and nano for my >examples: > >[weremouse@moonstudio ~]$ >cat /usr/share/applications/ubuntustudio-controls2.desktop [Desktop >Entry] Version=1.0 >Type=Application >StartupNotify=false >Terminal=false >Exec=roxterm --maximize -T "sudo >pluma /etc/security/limits.d/audio.conf" -e sudo >pluma /etc/security/limits.d/audio.conf Icon=ubuntustudio-logo >Name=Ubuntu Studio Controls 2 - sudo >pluma /etc/security/limits.d/audio.conf >Categories=System;Documentation; > > >[weremouse@moonstudio ~]$ >cat /usr/share/applications/ubuntustudio-controls3.desktop [Desktop >Entry] Version=1.0 >Type=Application >StartupNotify=false >Terminal=false >Exec=roxterm --maximize -T "sudo >nano /etc/security/limits.d/audio.conf" -e sudo >nano /etc/security/limits.d/audio.conf Icon=ubuntustudio-logo >Name=Ubuntu Studio Controls 3 - sudo >nano /etc/security/limits.d/audio.conf Categories=System;Documentation; > > >[weremouse@moonstudio ~]$ cat /etc/security/limits.d/audio.conf ># Changes to this file will be preserved. ># ># If you want to enable/disable realtime permissions, do not run ># ># dpkg-reconfigure -p high jackd ># ># See http://jackaudio.org/faq/linux_rt_config.html. ># ># Lines that start with a # are commented out. This means blah blah ... ># We named the group "audio", but you can chose any name for the group, ># e.g. "realtime". ># The FAQ already mention that nice values are complete nonsense, so ># it's wise to remove even a commented out entry. ># To lower the rtprio is similar absurd. It's said that very seldom it ># might prevent a weak computer against getting unresponsive, but ># usually this never happens. Blah blah ... ># ># Blah blah ... ># ># You should keep the Ubuntu Studio default settings: ># ># @audio - rtprio 99 ># @audio - memlock unlimited > >@audio - rtprio 99 >@audio - memlock unlimited > >As default editor I'm against vi(m), even the help of nano might be >confusing for newbies. I anyway recommend usage of nano. > >[weremouse@moonstudio ~]$ printf "$EDITOR \n---\n"; grep >EDITOR .bashrc nano >--- >export EDITOR="nano" > >Roxterm could be replaced by xfce4-terminal, but I strongly discourage >to stay with xfce4-terminal as the default terminal. > >Newbies are more likely willing to use a terminal, if it's as easy >usable and as convenient as an Internet browser. > >If you resize the Roxterm window, the line breaks automatically get >fixed. >You can use Ctrl++, Ctrl+- and Ctrl+0 to zoom, as you do for a web >browser. > >A desktop shortcut Ctrl+Alt+T is useful, it's corresponding to the >default ROXterm shortcut and could be mentioned by the menu name. >Perhaps changing it to Ctrl+T, the common web browser default, could be >considered. > >For openbox it would be > >[weremouse@moonstudio ~]$ grep -B2 -A2 rox .config/openbox/rc.xml > <keybind key="C-A-t"> > <action name="Execute"> > <command>roxterm --maximize --tab</command> > </action> > </keybind> > >Xfwm/Xfce likely provide this feature too. > >I added a menu entry "Actions" providing desktop shortcuts. > >Regards, >Ralf
PS: I forgot to add the file path and name to the comments (# /etc/security/limits.d/audio.conf), and the terminal should show a prompt (PS1 sudo editor /etc/security/limits.d/audio.conf). This could be realised, if the desktop file runs a script instead of directly launching the editor. But I would run sudo in a terminal instead of a pkexec solution. GUIs for simple things make Linux look like a restricted OS. -- ubuntu-studio-devel mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel
