How to install omxiv

Hi is there a way to install omxiv ? its in

I have try but was unable to install.
Any here that have manage to install?

@helio58 yes there is. You need to install omxplayer (apt-get install omxplayer), and copy contents of opt dir from to your opt dir e.g. via SCP, then follow instruction

I have another problem though. Everything is working but I want to restict use of omxiv/omxplayer to separate ssh account which cannot access antything but its folder. How do I do that? Please help!

WarHawk thank you for the links, but sadly I lack the understanding how to apply them to my situation.

I have built and installed omxiv, and installed omxplayer as root. It works fine. Now I will create a new user - and what do I need to do? Build&install omxiv, install omxplayer as that user, then apply restrictions to that new user with chroot instruction from the first link?

First of all, you should not copy manually and only the /opt/vc content. You might end with non-matching versions or worse, a broken system.
This firmware is applied on RPi via the raspberrypi-kernel|bootloader|0|bin packages, so a simple apt update && apt full-upgrade will bring everything onto current stage, or use dietpi-config > Advanced Options > Firmware update which applies the slightly newer master branch, but all this done in a careful way.

The guide in the first link is the effective way to completely jail the user. But as you can see, this requires to copy all required binaries and libraries into the chroot environment. So you need to identify everything that is required for omxiv and make it available within the chroot environment. Some /dev /sys /proc files might be required as well.
At least I would not create copies, but hardlinks via cp -l -v source dest, so no doubled disk space is used and APT updates are applied to the chroot environment as well.

I am trying to implement chroot according to Tecmint guide… how do I determine what do I need for omxplayer to work, apart from its shared libraries?

Not sure, it needs ALSA and dbus access, besides the above mentioned, /run ist most likely required to allow access to the dbus socket. Not sure how ALSA access technically works. Why not simply try and error? Nothing to loose and I guess starting omxplayer from inside the chroot then should give some error message from where additional needs can be hopefully derived.

First of all, thank you for support. Most people just ignore me whenever I ask related questions, making me feel like an idiot. )=

Omxplayer has a very bloody long dependencies list, it gets me depressed just looking at it. Frankly even following the guide to enable shell was a chore because libs are stored in different folders. Can I do something to restrict regular user from accessing stuff with creating a chroot jail, e.g. with user permissions like on Windows - or will it be insecure?

Of course you can solve it via user permissions as well, but the basic issues stays the same that you need to know which files/dirs access is required to and which not. So actually the chroot is easier then since the other way round you would need to adjust permissions for every single file that you want to block access for the user. And this can even break other stuff and new files/dirs are by default world-readable.

Another idea is to only allow the user to run a single command (omxplayer) + perhaps logout/exit:
IMP easier than setting an empty string alias for every single existing command would be to override the PATH variable for this user to e.g. /home//bin and symlink the commands there that you want it to be able to call. By this at least practically changing dir, reading files etc. is not possible without the need for chroot. But I guess rbash is saver to block this on a lower level.