Linux - Newbie This Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place! |
Notices |
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
|
|
07-06-2004, 09:46 AM
|
#1
|
LQ Newbie
Registered: Jul 2004
Distribution: Slackware 10
Posts: 20
Rep:
|
Tarballs installing questions
Hello,
I've recently installed Slackware 10.0 and want to install some
software. Previously, I had Knoppix with it's 'apt-get' package
managemant.
Now, there are tarballs in Slack, so I have a simple question...
... I dowloaded some software and after decopressing it I usally
have two folders: "usr" and "bin". I found I can run program
directly from bin, however I'd like to ask what is "doinst.sh"
in "install" folder? I supoose it is intended to install application,
but how to run it?
Thanks in advance and greets,
|
|
|
07-06-2004, 10:09 AM
|
#2
|
Member
Registered: Nov 2003
Location: Northcliffe, WA
Distribution: Slackware 12.0
Posts: 481
Rep:
|
./doinst.sh
or
sh doinst.sh
if that doesnt work try
chmod +x doinst.sh
./doinst.sh
|
|
|
07-06-2004, 10:15 AM
|
#3
|
LQ Newbie
Registered: Jul 2004
Distribution: Slackware 10
Posts: 20
Original Poster
Rep:
|
Thanks o lot :-)
"./" tells bash to exectute it as "sh" am I right?
|
|
|
07-06-2004, 10:16 AM
|
#4
|
LQ Newbie
Registered: Jul 2004
Distribution: Slackware 10
Posts: 20
Original Poster
Rep:
|
If I install any softare as a root will other user see this software or shall I simply
istall it as a user??
|
|
|
07-06-2004, 10:23 AM
|
#5
|
Member
Registered: Aug 2003
Location: N.C.
Distribution: rh9, fc1, slack 9.1, 10
Posts: 229
Rep:
|
it may seem overly obvious, but i'm going to say it anyway...
when issuing the ./doinstall.sh command, make sure that your current working directory is the same as the one that contains this script. the ./ is telling the system "in this directory." you could possibly run a script that you don't intend if you were to give this command from another directory (assuming that other directory contained a file named doinst.sh).
this may not seem like a big issue, since you may not often find scripts named doinst.sh, but consider giving a ./configure command from the wrong directory. configure scripts are everywhere. you can check your working directory with the command pwd.
|
|
|
07-06-2004, 10:27 AM
|
#6
|
Member
Registered: Aug 2003
Location: N.C.
Distribution: rh9, fc1, slack 9.1, 10
Posts: 229
Rep:
|
as stated above, the ./ tells the system that the executable script is in this current working directory, so execute it. when you normally give a command the system checks the directories in your $PATH environment variable for that executable. if it isn't found in those directories, then you get the "command not found" error. you can find out what directories are in your PATH by giving the command hope this helps.
|
|
|
07-06-2004, 11:10 AM
|
#7
|
LQ Newbie
Registered: Jul 2004
Distribution: Slackware 10
Posts: 20
Original Poster
Rep:
|
Hello,
well, I got your point. And yes, I had to use chmod +x (i guess it gives permission to
execute...).
But I tried it on many install scripts and I am gettin messages like "Broken symbolic link
to..."
What could be the problem?
|
|
|
07-06-2004, 08:51 PM
|
#8
|
Member
Registered: Nov 2003
Location: Northcliffe, WA
Distribution: Slackware 12.0
Posts: 481
Rep:
|
A symbolic link is like a windows shortcut, type
ls -l <filename>
to show where abouts a file is supposed to be linked to.
./ tells bash to execute the file from the current directory.
If the tarball has a /usr and /bin directory it is possibly a slackware package
in which case you can use installpkg as root to install it.
|
|
|
All times are GMT -5. The time now is 04:21 AM.
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|