Posts by chewitt

    There are more NUC variants than anyone cares to keep tabs upon these days so rather than ask if there are any known issues with a specific model, it's much easier to just stick the latest nightly LE image on a USB stick and try it - then come back if there are problems.

    Safe mode only applies when the OS is fine but something got messed up with Kodi (normally a bad add-on causing repeated crashing). In your case something more fundamental is messed up and you're not getting that far in the boot process. The OS does (or should) attempt to fix basic filesystem issues automagically but there are limits to that. NB: If you aren't familiar with Linux and only used the USB a few times it'll be easier abd considerably quicker to start over with a clean install.

    It's just installed to /storage/.config/samba.conf (rename the .sample file). It's the same process as any other OS but ISTR we are missing the tools needed to create the password database, so you'll have to do that somewhere else then move the file to LE and reference where it resides in the conf.

    No idea on the performance drop/difference with containers as it's not the kind of thing we ever have time for - but it's $free to experiment.

    LE has a samba server embedded but it assumes a single user so you will need to deploy a customised .conf to support different configs with multiple users and any extra configuration required. LE has no package manager but you can install the Docker add-on to add containers to extend other capabilities and functions. There are deliberately no torrent add-ons in our repo.

    The one thing I notice is .. when scrolling with some cheapo IR remote (via sensor) the scrolling in menus is staggeringly slow compared to the BT remote that I normally use, or a USB keyboard - it's all about the repeat rate which is higher on the latter devices. In terms of actual GUI refresh rate it's running at 60fps and I don't see any issues with it being slow, and RPi4 was definitely a noticeable improvement over RPi3B+ that I used before. You might need to be more specific about what aspect of GUI performance you're trying to complain about.

    LE is a complete OS not an App, so you cannot run it from within Windows. And nano is a Linux text editor; like notepad, but run from the Linux command shell, it's not a GUI app.

    It's hard to comment on what's happened, but either the SD cards are old/bad/dying which leads to corruption and issues or perhaps you're powering off the machines without clean shutdown and causing filesystem problems on the cards. Linux is a lot more sensitive to that kind of thing than Windows; it will fail loudly and early whereas Windows sort of blindly continues giving the appearance of normal while secretly trashing your data.

    Install LE 9.2.8 (as you need optimised HEVC support). Install inputstream.adaptive from the LE repo. Install the Netflix add-on repo. Install Netflix add-on from the repo. Setup the user/pass and on first play inputstream.adaptive should install the widevine.helper add-on which will download and install the needed Widevine CDM library for Kodi use. This takes a while, but once done you should be able to play something (720p max). That's how it worked last time I did it (some time ago, I don't use Netflix often).

    Linux makes things read-only to prevent filesystem damage when it detects corruption or the filesystem in an unclean state. On removable drives this is normally due to not disconnecting/ejecting the drive cleanly. If the filesystem is NTFS or eFAT, reconnect to Windows, use chkdsk and then eject properly. Assuming that resolved the issue, Linux should then mount the drive in RW mode. If the drive is HFS+ (Apple) then you're screwed because Linux doesn't support RW access and will always mount RO, and you'll need to reformat the drive to exFAT to use the drive with LE.

    If you want to place something in /storage you first need to create a package (or ammend an existing one) to embed the file(s) somewhere in the SYSTEM file and then embed and execute a script (or systemd service which executes a script) at boot time that checks if the file(s) exist on /storage and if not, copies them there. You cannot create files directly on /storage via the buildsystem because that path doesn't (and should not) exist in the SYSTEM or KERNEL files.

    NB: There is no direct mapping from /storage/.config to /etc .. we typically configure a package to run from /var/run/something which is symlinked to a location in /etc and then systemd services (which run scripts) copy the content from /storage/.config/something to /var/run/something at boot time to make things appear as if they are mapped. There's lots of prior art for this in the systemd package.