[SOLVED] sudo and install.sh

Pedroski · 03-21-2018, 07:28 PM

Hi, I am trying to install Epson's imagescan for my DS-510 batch scanner. I have done this before on my newer laptop no problem. I do not know why sudo can't find install.sh on this older Ubuntu 14.04 laptop.

I can, for example enter sudo gedit and open any file. So I think sudo is working correctly.

Quote:

pedro@pedro-bedro2:~/Downloads/imagescan-bundle-ubuntu-14.04-1.3.26.x86.deb$ dir core install.sh plugins README.rst
pedro@pedro-bedro2:~/Downloads/image...1.3.26.x86.deb$ sudo ./install.sh
sudo: ./install.sh: command not found
pedro@pedro-bedro2:~/Downloads/image...1.3.26.x86.deb$

When I enter sudo ./install.sh I get 'command not found'

This must be a path problem I guess. How to make install.sh start?

hydrurga · 03-21-2018, 07:31 PM

It may not be executable (yet), especially if you have just downloaded it.

Try:

Code:

chmod +x ./install.sh

hydrurga · 03-21-2018, 07:34 PM

As a follow-up, are you sure that you should be using sudo? That's not what I have in the instructions I got from Epson for my scanner. I think the program itself asks for privileges when it requires them.

Pedroski · 03-21-2018, 07:46 PM

It was the execute as program bit, that's all! Thanks, I didn't think of that!

This is the version for Ubu 14.04, the read me says enter sudo ./install.sh

I use Formreturn to set lots of multiple choice tests. I lost my Formreturn DB, it got corrupted somehow. This week's work was lost. Now I have installed a copy of everything on this old laptop. If I lose 1, I can still use the copy on here!

hydrurga · 03-21-2018, 07:52 PM

Quote:

Originally Posted by Pedroski

It was the execute as program bit, that's all! Thanks, I didn't think of that!

This is the version for Ubu 14.04, the read me says enter sudo ./install.sh

I use Formreturn to set lots of multiple choice tests. I lost my Formreturn DB, it got corrupted somehow. This week's work was lost. Now I have installed a copy of everything on this old laptop. If I lose 1, I can still use the copy on here!

Good to hear (the problem resolution, not the fact that you lost several days of work, always a bummer). You should think about daily database backups, even more if there is a large throughput of data (you don't need to backup to a laptop throughout the day, even a USB stick would do, ensuring that your backups are separate to avoid overwriting a good one with a corrupted one).