Posts by lrusak

Quote from tstones

Thanks

there is a bug in the packaging so the file doesn't get included in the tarball.

You can just get the tool here create_virtualimage

Quote from jjbull

I'm looking to install Hyperion
It mentions on the download place that the addon repo has chromium Hyperion etc I have no libreelec repo in my list or am I being totally stupid here I upgraded from oe not sure if that makes a difference or have I missed the repo address somewhere
[hr]
I'm either blind or stupid it's there now since the latest update
[hr]
Can someone make an idiots guide to get this working looking to sort the software side out first,
Found a guide and I know it needs compiling but when I tried it message came up about libreelec not needing "sudo" ????

Display More

install Hyperion from the LibreELEC repo, then place hyperion.config.json into the service.hyperion folder in the Userdata SMB share.

if you don't have a hyperion.config.json you need to make one or copy the sample one via ssh

cp /storage/.kodi/addons/service.hyperion/config/hyperion.config.json.sample /storage/.kodi/userdata/addon_data/service.hyperion/hyperion.config.json

then edit it there

Quote from Loggio

Hi,

as the title suggests, i cannot use TVHeadend 4.2 , it will not detect my adapter.
My adapter is a HDhomerun.

the "adapters" page seems faulty.
when i click on adapters it doesn't bring down a drop list.
The tuner is detected in:
addon_data\service.tvheadend42\input\tvhdhomerun\adapters\84fd31dbe49f543d68665546a88c2e65

but does not display in tvheadend 4.2

If i install tvheadend 4.0 it works as usual

Display More

This should be fixed in the latest tvheadend 4.2, which should be built and pushed to the repo soon

Quote from JohnBoyz

I probably placed the above line in an incorrect position in the file, but the result was that I had no partitions auto mounted on boot up, but also I could not find a means to locate and mount any partition I might need, except on the network of course. I successfully mounted a network partition.

All I want to achieve is not to have the partitions mounted, but to have their presence recognised and have them made available for mounting through the filemanager.

Is it achievable?

Nope. What's wrong with having them mounted?

The only thing you could really do is create systemd automount services, but this isn't really a good solution.

no if the file has the same name it will override the original

Quote from JohnBoyz

I think it should be possible to unsquash the SYSTEM file, edit some rule and then mksquash again.
This would work?

I would need to know what options to use for the mksquash command and also what edit to apply to which file ..... maybe
/usr/lib/udev/rules.d/95-udevil-mount.rules ?

If this would work can you (or anyone else) provide the info needed?

Thanks.

don't bother, just copy the file to where it is editable

cp /usr/lib/udev/rules.d/95-udevil-mount.rules /storage/.config/udev.rules.d/

you'll probably want something like

SUBSYSTEM=="block", GOTO="exit"