I recently configured and made the drivers for my wacom device. It installed okay, the drivers seem to be working, and there were no errors in the configure and make process.
However, one application that was supposed to be isntalled is a graphical tablet configuration utility called wacomcpl. So far as I know, it should be installed. But perhaps it is somewhere that is not included in the path. But I have no idea where the program would have been installed to.
I can't find by Google the right command on the net to find out where an application is, although I'm sure it exists. What should I do to try and find an application called wacomcpl on my system?
Dave
On Mon, August 1, 2005 10:51 am, Dave Gutteridge said:
I recently configured and made the drivers for my wacom device. It
installed okay, the drivers seem to be working, and there were no errors in the configure and make process.
However, one application that was supposed to be isntalled is a
graphical tablet configuration utility called wacomcpl. So far as I know, it should be installed. But perhaps it is somewhere that is not included in the path. But I have no idea where the program would have been installed to.
I can't find by Google the right command on the net to find out
where an application is, although I'm sure it exists. What should I do to try and find an application called wacomcpl on my system?
Dave _______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
You can issue this command to find that program (if it exists) on your machine:
find / -name 'wacomcpl'
On Aug 1, 2005, at 12:20 PM, Dave Gutteridge wrote:
Great! Thank you. Turns out it was in /usr/bin/local. I would have thought /usr/bin/local would be on the default path. Can I set it to be?
do you mean /usr/local/bin? /usr/bin/local is pretty nonstandard.
SIMPLE ANSWER: set your $PATH environment variable in ~/.profile. this command will do it:
echo "export PATH=$PATH:/usr/local/bin" >> ~/.profile
close your terminal window, open a new one, and you're good to go.
MORE COMPLEX ANSWER: the simple answer only sets this variable for one user, you. Red Hat provides you will a straightforward facility for setting the variable for all users on the system: the /etc/ profile.d directory.
look in /etc/profile.d - you'll find a number of files called something.sh and something.csh. each of the something.sh files are written in Bourne shell syntax and will be read by bash/ksh when they initialize; the something.csh files are written in C shell syntax and will be read by tcsh/csh when they initialize. you could create a file called path.sh that looked something like this:
# path customizations export PATH=$PATH:/usr/local/bin
and another called path.csh that looked something like this:
# path customizations setenv PATH "$PATH:/usr/local/bin"
and then all new instances of shells systemwide would adopt the new settings. also, since these new files you'd create would not be owned by any package, you shouldn't have to worry about them being clobbered during software updates.
-steve
p.s. one tip that may save you a long "find /" in the future; rpm -ql <packagename> gives you a list of all files contained in a given package. "rpm -ql wacom | grep wacomcpl" might have been a quicker route to success (assuming the wacom package was named something like wacom.x.y-z.i386.rpm)
--- If this were played upon a stage now, I could condemn it as an improbable fiction. - Fabian, Twelfth Night, III,v
Steve,
Thank you for the answer and explanation. That sets the situation competely straight for me.
Dave
On Mon, August 1, 2005 11:41 am, Steve Huff said:
p.s. one tip that may save you a long "find /" in the future; rpm -ql <packagename> gives you a list of all files contained in a given package. "rpm -ql wacom | grep wacomcpl" might have been a quicker route to success (assuming the wacom package was named something like wacom.x.y-z.i386.rpm)
This is true for rpm packages, but the original post said the drivers were made and installed ... I assumed that those were not an RPM, but they could have been.
Another thing that can be done is to install slocate and set the command updatedb to run in cron, then you can use the command:
locate name_of_file
This is much faster than find, but only if the slocate database is kept updated.
This is true for rpm packages, but the original post said the drivers were made and installed ... I assumed that those were not an RPM, but they could have been.
Just in case it matters... the installed application was not an RPM. It's this really difficult to install driver for Wacom tablets. The guys who make it are working hard and it's a great effort to provide a driver for a device when the manufacturer doesn't. But still, it's really complicated and it seems every step has to be done by hand - combined with a lot of patience.
Dave