It would appear that on Aug 22, Carlos E. R. did say:
On 2010-08-22 19:45, Joe(theWordy)Philbrook wrote:
What do I need to put in a cli command besides /sbin/yast2 to trigger the authentication prompt box???
You need a tool such as "gnomesu" or "kdesu" for xfsce or enlightment.
Or, you can simply open an xterm, there issue "su -", password, and "yast2 &"
I'd rather not do this via an xterm that I'd have to close. especially one that leaves an open root command prompt laying around... Though I suppose that for the I manually added e16 menu I might keep a menu entry of: " Control Center" NULL exec "xterm -e su -c /sbin/yast2" I didn't need the extra "-" arg in the "su - -c /sbin/yast2" somebody suggested...
On Sun, Aug 22, 2010 at 09:46:52PM +0200, Carlos E. R. wrote:
On 2010-08-22 20:51, Mark Goldstein wrote:
On Sun, Aug 22, 2010 at 9:44 PM, Carlos E. R. <> wrote:
Or sudo :-)
sudo would not set $DISPLAY properly and ncurses version of yast will run (maybe there is some option, but I don't know it). su - create normal root environment.
Mmmm... didn't think of that.
Incidentally I found the sudo version to be an interesting alternative (once I set the font size to something legible " Text-mode yast2" NULL exec "xterm -fn 12x24 -e sudo /sbin/yast2"
xdg-su /sbin/yast2
One last point. Both xdg-su and kdesu are installed but
xdg-su /sbin/yast2
fails to do anything while
kdesu /sbin/yast2
works except that like sudo it remembers the previous successful root
passwd for a while. (This is NOT so good) If I had wanted one root
password entry to be good for several commands I'd have just opened a
root shell... (sigh)
Ah well I guess it's either that or put up with the unsightly xterm hanging
around until I close yast2
In any case, Thanks one & all for the kind suggestions. They helped
--
| --- ___
| <0> <-> Joe (theWordy) Philbrook
| ^ J(tWdy)P
| ~\___/~ <