Salix Forums

Not a Problem..Not Useless Talk..
So I placed this in Misc..

Maybe this will help Someone Else.

I added an Xfce4 Desktop on top of my Salix KDE 13.1 install...
I was Happy!

However while I installed all Xfce4 packages from Gslapt Salix std repositories..some items were missing such as gksu (Which will launch a root user GUI app) i.e. Gslapt

..Without gksu some Xfce menu items such as Gslapt...will not open
To make my Xfce4 add on Desktop environment more useful I proceeded to add gksu..
To do this I had to enlist the use of
these items in this Order for Dependency reasons
..other Dependencies were in place..ie (gnome-keyring & Gconf etc )
A. Packages ready to be added on Gslapt repositories
......linuxdoc-tools...

B. A download of gtk-doc from GNOME/sources
......gtk-doc-1.18

C. SlackBuilds.org packages for 13.1
.....libgtop..libgksu..gksu

The above is the simple needed order to arrive at a gksu install..

I however began from gksu in SlackBuilds. Discovered by error or reading those missing dependencies and then backtracked to correct the deficiencies.

Working out of slackbuilds.org I prepared to add the gksu.
...Downloads

First stop gksu for 13.1.

gksu.SlackBuild
This requires libgksu.

So..installed
libgksu
This requires GConf, libgtop, and gnome-keyring.

So.. Salix 13.1 was missing libgtop
..Next Installed libgtop SlackBuild

Next all that was left was to install/Slackbuild the gksu.

Problem, during the build the build failed because could not FIND
gtkdoc-scan... which is part of the gtkdoc group..This does not exist in in SlackBuilds but I found a site to download the src to try a (./configure..make..make install.)

* I downloaded gtk-doc 1.18 from
http://ftp.gnome.org/pub/GNOME/sources/gtk-doc/
Extracted it to the Home dir and worked out of that Dir..
This includes............
gtkdoc-check, gtkdoc-depscan, gtkdoc-fixxref, gtkdocize, gtkdoc-mkdb, gtkdoc-mkhtml, gtkdoc-mkman, gtkdoc-mkpdf, gtkdoc-mktmpl, gtkdoc-rebase, gtkdoc-scan, gtkdoc-scangobj, and gtkdoc-scanobj

However that required that linuxdoc-tools was installed per GSlapt
..Next Installed linuxdoc-tools

Finally, back to run the gksu dir and run the gksu Slackbuild..

As each is Downloaded then extracted from Download to a folder in the Home dir to look like....
sqlpython[~]$ ls
Desktop NetBeansProjects cxoffice memo_file
Development Pictures gksu netbeans-7.0
Documents Public gtk-doc-1.18 qtcreator-2.3.0
Downloads SharedDocs jdk1.6.0_26 skype_static-2.1.0.81
Music TestQT libgksu
MyMemos Videos libgtop

Once built they appear in the /tmp Dir as so

root[tmp]# ls *.tgz
gksu-2.0.0-i486-1_SBo.tgz
google-chrome-9.0.597.84-i386-1_SBo.tgz
libgksu-2.0.7-i486-1_SBo.tgz
libgtop-2.24.0-i486-1_SBo.tgz
mysql-workbench-gpl-5.2.29-i486-1_SBo.tgz

Following the How To steps in SlackBuilds.org in installed each Build..
1. Download Slackbuild and it's Source
2. Extract to it's own dir for Build
3. Place Down Loaded source in Extracted Source dir
4. Run in Build Dir executable Build ./SlackBuild (checking 1st the Version # in Script matches Source Version#)
5. CD to /tmp and install package (installpkg buildpackagename.tgz)

OR
If you need/want a gksu ... try to use an Install that includes it already such as Salix Xfce4 ..

Why didn't you just install ktsuss, which includes a wrapper for gksu?

S
While wrappers have their place...
I prefer to keep my linux installs as close to original as possible.
For me it was worth the effort to install gksu...

That is One but more then that I try not to use wrappers. After years of using ndiswrapper with bcm43xx and nspluginwrapper & Flash with my 64bit system installs...they are just an extra job on each install.

Plus I don't like the little graphical prompt employed by ktsuss..just give me the password. I don't need no stinkin.. UserName.
I will be using root anyway.

Lastly, no one gets away with calling me Stupid...except my wife...

ktsuss stands for "keep the su simple, stupid"

Seriously,

If I can avoid wrappers I will.
The minute the Original shows up I'm on it..Like once we got the bcm43xx firmware, I couldn't wait dump ndiswrapper fast. Although, I had used it for years.

As with all wrappers, not an official component of the Linux Kernel and always a possible security hole. As Ndiswrapper 1.53 once did. Wrappers by envelope design only give another area to breach. Especially those dealing with networks and passwords.. There is enough addon stuff we are using without choosing those that are uncommon.

So, Unless I am absolutely w/o alternative I will pass on the password wrapper..Pun Intended...

I also Drink Real Coke..with Real Sugar and Real Caffiene..

None of that Caffiene Free Diet Coke crap for me.. and I don't care if that offends the Diet Coca-Cola Drinkers..

sqlpython wrote:S
While wrappers have their place...
I prefer to keep my linux installs as close to original as possible.
For me it was worth the effort to install gksu...

There is no gksu anymore. The original gksu is abandoned, old, unmaintained with a lot of issues that will never be fixed. gksu-polkit is its successor, but that's not ready yet, it has lots of stability issues and there is no idea when it's going to be fixed, if ever.

sqlpython wrote:That is One but more then that I try not to use wrappers. After years of using ndiswrapper with bcm43xx and nspluginwrapper & Flash with my 64bit system installs...they are just an extra job on each install.

You are really confused. Totally different kind of wrapper.

sqlpython wrote:Plus I don't like the little graphical prompt employed by ktsuss..just give me the password. I don't need no stinkin.. UserName.
I will be using root anyway.

You haven't really used our ktsuss package, have you?

sqlpython wrote:Seriously,
If I can avoid wrappers I will.

So, don't eat candy for the rest of your life.

sqlpython wrote:The minute the Original shows up I'm on it..Like once we got the bcm43xx firmware, I couldn't wait dump ndiswrapper fast. Although, I had used it for years.

Once again, totally different kind of wrapper.

sqlpython wrote:As with all wrappers, not an official component of the Linux Kernel and always a possible security hole. As Ndiswrapper 1.53 once did. Wrappers by envelope design only give another area to breach. Especially those dealing with networks and passwords.. There is enough addon stuff we are using without choosing those that are uncommon.

Once again, totally different kind of wrapper.

sqlpython wrote:So, Unless I am absolutely w/o alternative I will pass on the password wrapper..Pun Intended...

Once again, totally different kind of wrapper.

sqlpython wrote:I also Drink Real Coke..with Real Sugar and Real Caffiene..

None of that Caffiene Free Diet Coke crap for me.. and I don't care if that offends the Diet Coca-Cola Drinkers..

So use a Real root password command prompt.

Hi Gapan,
Someone doesn't support gksu use..

I installed gksu because it comes on all my installs ready to use and simply want to continue the same on my Salix install..

I didn't start this thread to explain my use of gksu over ktsuss or even a Real Root password prompt.
This thread was just a simple explanation of how I installed gksu when it went missing. A utility that I have been using for years. that I like which works just fine in all my installs..Period.

When I publish a topic such as this one. I do so only to give a read for others that may want a How To IF they choose to install the same.
However as both yourself and Shador are very active contributors here I am happy to explain my choice here.

I understand and appreciate that you both are pointing out that there is another road but then there always is another way with Linux.
I can't say that I will Never find myself Ever using ktsuss but not now. Not when all my other installs happily use gtksu.
Once upon a time I used the FVWM desktop and EMACS along with a Lynx web browser.

Though, You are not spot on in some assessments. Let me address a few points.

There is no gksu anymore.?

It is there and being supported for now by Debian. Perhaps it doesn't have an on going separate Dev team but Debian keeps it compiled and packaged & on going for each distro...etch, lenny, squeeze, wheezy and sid.. and does Bug stomping.
Also I am sure there will be one be for the next Debian beyond Wheezy and Sid.
It is Not the original but what I use on Debian & Other installs as gksu works fine..has for many years.. I will continue to use it until if shows me regular failings and has yet to show me any.

Once again, totally different kind of wrapper.

No argument but a wrapper all the same.... my choice to avoid.
Some Wrappers have found their place as acceptable such as TCP wrappers and while the are convenient running on the application layer they do have some issues...
Firstly, apps must be compiled with the libwrap library.
Also wrappers willnot work with RPC services over TCP.
And last I knew, the user name lookup feature of TCP Wrappers uses identd to identify the username of the remote host. By default, this feature is disabled, as identd may appear hung when there are large number of TCP connections.
Wrappers serve as good work arounds but do bring baggage.

So use a Real root password command prompt.

Once again not what I want to use on my systems...which is why I installed gksu..which works just fine.
....that choice also exists for ktsuss current users
IF and when gksu shows me quirky behavior or fails I will fall in line behind you and replace it.
However It works now on all my systems and has always worked. If it is giving you problems somehow.... Sorry! but not me.

vive gksu ...

Your still missing the point. The wrapper script that I wrote just removes the requirement to specify the root user when launching ktsuss which is the default behaviour for applications such as kdesu and gksu.

If your unsure what's going on here just read the script:

Code: Select all

#!/bin/sh

# /usr/bin/gksu: ktsuss wrapper

PATH="${PATH}:/sbin:/usr/sbin:/usr/local/sbin"

help() {
	cat <<- EOF
	Usage: gksu [OPTION] command [COMMAND ARGUMENTS]
	Run a command as another user
	
	OPTIONS:
	        -u, --user USER      Runs the command as the given user
	        -h, --help           Show this help
	EOF
}

case $1 in
	-h | --help | "" )
	help
	exit
	;;
	-u | --user )
	USER="$2"
	shift 2
	;;
	* )
	USER="root"
	;;
esac

CMD="$@"

if [ -x "`type -path ktsuss`" ]; then
  KTSUSS="`type -path ktsuss` -u $USER"
else
  echo "$(basename $0): \`ktsuss' command not found"
  exit 1
fi

eval "$KTSUSS" "$CMD"

If gksu works for you then great but I, like George, don't really see the point when this works just as well.

I, like George, don't really see the point when this works just as well.

.
Not really a big deal just this.............
I have quite a few installs on many machines...11 currently (home and Office). All with multiple partition installs and some with multiple disks. While Linux is a tool it is also my hobby since 1995. So, as a Distro junkie I like to continually install and remove and modify my Distros. I also contribute and write software. What this means is that while these Distros may differ in their base (Debian/Slackware/Red Hat/BSD/Gentoo etc)
they must also all work alike for me as the user as well as the people for whom I do installs. I need continuity of Apps, Interface, passwords etc.. Look at one of my Distros installs you are looking at all.
From one Distro to another my goal is to get them to work alike.
Why?
Because when I am Modifying, DeBugging, Compiling, Programing etc.. I don't want to have to remember ANY nuances.. I have too much to remember across these installs as it is.. Every small variation is another small annoyance.. while small each concession to my work method adds up..
Every night I put my car keys in the same draw, my loose change in the same glass dish, My ties on the same rack, ..I sleep on the same side of the bed..the same place and motion for everything that I can reasonably enforce and control
Bottom line, when as example I hit Alt-F2 or type from the CLI I don't want to have to remember that this one Distro is ktsuss instead of gksu.
At the end of the day I am not rebelling against ktsuss. I am simply supporting my own conventions that make things simpler/happier for me.

BTW on your part ktsuss is a good contribution..

gapan wrote:
sqlpython wrote:I also Drink Real Coke..with Real Sugar and Real Caffiene..

None of that Caffiene Free Diet Coke crap for me.. and I don't care if that offends the Diet Coca-Cola Drinkers..
So use a Real root password command prompt.

+1
This gksu/ktsuss stuff is for wimps and posers only. Real men use a root prompt

This gksu/ktsuss stuff is for wimps and posers only. Real men use a root prompt

I am a Self Confessed Wimp...

.....................................................

Salix Forums

GKSU install added

GKSU install added

Re: GKSU install added

Re: GKSU install added

Re: GKSU install added

Re: GKSU install added

Re: GKSU install added

Re: GKSU install added

Re: GKSU install added

Re: GKSU install added