Guidedog IP masq prog. PATH prob

[mekon]

First time with a Linux box as an Internet gateway, thanks to Guarddog firewall GUI and Guidedog the IP masquerade program. Things have moved on a bit as I've got a Smoothwall on an old machine. But I want to fix Guidedog. I installed it off a tar.bz2, but think its installed it in the wrong place. I can run it off the CLI, su and path, then the GUI comes up. I ok it and it runs ok. Its put it in the following locations.
/usr/local/kde/bin
/usr/local/kde/lib
/usr/local/kde/share
/bin has got the executable in it. /lib has got a script in it. /share has got icons;doc;apps; and appink, which I copied to the desktop. If I run appink on the desktop, I get the request for root password. I input that and ok it and get a .exe trying to run in the taskbar, which then times out. Obviously not beeing able to find the path to the .exe .
Any ideas what I can do to link appink to the executable to start the program, I'm not bothered about the Guidedog icon not being on the desktop, but it would me nice to start the program from there. Mekon.

This is on FC1 by the way.

[crackers]

(There's no such thing as an ".exe" in the Linux world, by the way.)

Instead of copying the applnk, just right-click on the desktop, select "New->File->Link to Application" and enter the information in the dialog. The two tabs you're most interesting in are "General" (the name of the application shown on the desktop and the icon) and "Application" (Command). Use the command from the applink file (you can simply view it's properties) and you should be good to go.

[mekon]

thanks crackers for the help. Problem is I dont have an icon for Guidedog on the desktop. I 've got around the problem by installing the RH9 rpm on a test install of FC1, and it works ok, puts the icon on the desktop and works. I'd still like to know why the tarball install put all the stuff in /usr/local/kde/bin/guidedog. But the rpm install as with Guarddog the firewall GUI has put it all in subdirectories of /usr/share. Some of it in apps, some in applications, and a bit in appink. I'm not too clued up on moving files around, but if I made new subdirectories in /usr/share could I move the stuff from /usr/local/kde/bin that was put there from the tarball install, and the application would then work properly. Its a bit of an academic Q as the Guidedog application does work ok on FC1 from the RH9 rpm install. And as for your comment about .exe's, I'm glad to be free from the thro the roof security problems with XP. Its bad enough having FC2 now referring to directories as folders. Thats a real Kop-out. I did'nt mean to offend, and was just trying to make it clear that it contained the binary, and was'nt just a shell script or something else. Mekon

running:
FC1; FC2; MDK9,2; MDK10.0; Slackware10.0; Debian3.0 (few probs with that. no shutdown button on the login/logout screen). Gentoo 2004.2. this is another story, but a darned good learning curve for working with runlevel3. XP (and i'm sorry for swearing), but its got the synths and sequencers on it, but there just ai'nt the music making software there at the moment for Linux, Perhaps Wine will get there act together and stop trying to put MS office on Linux and gets some apps that there ar'nt no alternatives for on the Linux box.

machinery:
an old Gateway 500 (P111 katmai) 256MB RAM, 40GB HDD with win ME (not used much, but has Java Development Kit on it) 80GB HDD with MDK9.2 and a few partitions for backups for the linux OS's. 40GB HDD with FC1 and other stuff.
an Aiii-friend 1.3GHZ (celeron) fixed 40GB HDD NTFS (for the music stuff) , and a caddy for all the Linux OS's. IGB RAM.
Not really Hi-Tech, but it works.

[crackers]

The reason the binaries is in a different place is that the RH/Fedora packagers build the RPMs that way, whereas the source tarballs usually try to make no distinction for location and opt for the "least dangerous, pretty-close to universal option" as a default. Usually, you can over-ride this and get the same basic setup when running "./configure" by specifying the "--prefix=/usr" option.

As for installing cross-distribution RPMs (e.g. RH9 on FC1), sometimes you get lucky. Most times you don't. Ditto for moving files around - not all source tarballs produce binaries that are as nicely "behaved."

[mekon]

thanks crackers, for the reply. I'm glad the RH9 rpm worked on FC1 in this instance, especially as Guarddog and Guidedog are a couple of really good programs for setting up an Internet gateway. I'll leave shifting stuff around in the filesystem until i'm more skilled. Thanks again. Mekon.