Hi
Well, to keep this short, I have actually never had to run a .run file and had no clue.
I do not know why it is that different entities KNOW years ahead that they will be producing files to run on "Ubuntu or Debian" and don't "have the time / effort / whatever" to actually make a .deb file...I mean how many different OS files are there any considering the bajillion files that are produced yearly?
But, anyway...hplip has a .run file for my latest printer / scanner and although the driver for printing works very marvellously it did not scan.
when it was actually EXPLAINED the process is straightforward; involving making the file "executable", clicking it and and after a restart some terminal stuff using hp-setup.
I am going to quote the instructions on how to run a .run for Ubuntu just in case the link goes down and also provide a link to the original instructions:
Here is the link to the original page:
https://duckduckgo.com/?q=how+do+I+i...l&ia=qa&iax=qa
https://askubuntu.com/questions/1874...tall-run-files
and, as usual, if anyone has questions please ask.
woodsmoke
Well, to keep this short, I have actually never had to run a .run file and had no clue.
I do not know why it is that different entities KNOW years ahead that they will be producing files to run on "Ubuntu or Debian" and don't "have the time / effort / whatever" to actually make a .deb file...I mean how many different OS files are there any considering the bajillion files that are produced yearly?
But, anyway...hplip has a .run file for my latest printer / scanner and although the driver for printing works very marvellously it did not scan.
when it was actually EXPLAINED the process is straightforward; involving making the file "executable", clicking it and and after a restart some terminal stuff using hp-setup.
I am going to quote the instructions on how to run a .run for Ubuntu just in case the link goes down and also provide a link to the original instructions:
How do I install .run files
Occasionally, some applications and games (eg. some from the Humble Indie Bundle) have .run installers. Before installing using these, check to see if:
it is available from the Software Centre
it is available as a .deb file, which will open in the Software Center
You can install .run files from the graphical interface, but using a terminal is more likely to give you useful feedback. To install a .run file you need to:
make it executable.
execute it
This is because .run files are just executable programs that do some unknown magic to install the program. This is similar to what .exe installers do on Windows and is different to the normal methods (at best, using the Software Centre, at worst using .deb files) in which applications are installed in a standard way and can be easily removed.
Graphical Method
Right click on the file in the file manager and click 'Properties'. Click the 'Permissions' tab and tick the box that says 'Allow executing file as program'.
Double click the file to execute it.
If this method doesn't work, try using the terminal method.
Terminal Method
Assume the file is called some-app.run and is in the folder /home/user/Downloads. You will need to modify these instructions to fit your situation.
Open a terminal (Applications->Accessories->Terminal).
enter cd /home/user/Downloads
enter chmod +x some-app.run
enter ./some-app.run
if step 4 fails with a message including 'permission denied', try entering sudo ./some-app.run (you will need to enter your password for this).
Notes
Sometimes you will come across .bin files. These are basically the same as .run files.
The method to install .run files can be used to execute any file (as long as it has some sort of executable code in it.
Be careful using sudo and only use it when absolutely required. Translated into English, it means 'Run this command but allow it to do anything it wants to my computer'. This is why you are prompted for your password.
Occasionally, some applications and games (eg. some from the Humble Indie Bundle) have .run installers. Before installing using these, check to see if:
it is available from the Software Centre
it is available as a .deb file, which will open in the Software Center
You can install .run files from the graphical interface, but using a terminal is more likely to give you useful feedback. To install a .run file you need to:
make it executable.
execute it
This is because .run files are just executable programs that do some unknown magic to install the program. This is similar to what .exe installers do on Windows and is different to the normal methods (at best, using the Software Centre, at worst using .deb files) in which applications are installed in a standard way and can be easily removed.
Graphical Method
Right click on the file in the file manager and click 'Properties'. Click the 'Permissions' tab and tick the box that says 'Allow executing file as program'.
Double click the file to execute it.
If this method doesn't work, try using the terminal method.
Terminal Method
Assume the file is called some-app.run and is in the folder /home/user/Downloads. You will need to modify these instructions to fit your situation.
Open a terminal (Applications->Accessories->Terminal).
enter cd /home/user/Downloads
enter chmod +x some-app.run
enter ./some-app.run
if step 4 fails with a message including 'permission denied', try entering sudo ./some-app.run (you will need to enter your password for this).
Notes
Sometimes you will come across .bin files. These are basically the same as .run files.
The method to install .run files can be used to execute any file (as long as it has some sort of executable code in it.
Be careful using sudo and only use it when absolutely required. Translated into English, it means 'Run this command but allow it to do anything it wants to my computer'. This is why you are prompted for your password.
https://duckduckgo.com/?q=how+do+I+i...l&ia=qa&iax=qa
https://askubuntu.com/questions/1874...tall-run-files
and, as usual, if anyone has questions please ask.
woodsmoke