Linux - NewbieThis 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.
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.
I've recently reinstalled everyting on my computer. When it came to reinstall eciadsl I took the package I used before(I kept it on my system, save redownloading it), and tried to install the Slackware package using "installpkg". However, it executes the install process then when it gets to "executing install script..." it just exits out of the install and returns me to the shell and does nothing. I'm installing it as root too.
Distribution: Slackware64 14.2 and current, SlackwareARM current
Posts: 1,645
Rep:
Sounds like the normal behaviour -- the install script usually just creates symbolic links to installed binaries and/or libraries, nothing else. It should be installed ok I guess.
If you want to check this create some empty folder where you can play around, go there and do an "explodepkg eciadsl......tgz" (replace with your package's name) and then type "less install/doinst.sh", then you see what the install script is all about.
Are you saying that it installed correctly? Because if so, I don't think it worked. If I remember correctly, last time I installed this, after installation I had to type "eciadls-config-tk" to configue it. However, I tried to do that thinking it had installed but I got a "command not recognised". So I don't think it did install.
Distribution: Slackware64 14.2 and current, SlackwareARM current
Posts: 1,645
Rep:
I can't definitely say if your package is installed correctly. I was just saying that the message you described and that nothing great happens after that is normal when installing most packages.
If you unpack the package (the "explodepkg" I mentioned) or look in the according file in /var/log/packages you see which files should have been installed -- and if eciadls-config-tk or any other file is listed there.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.