The entire OS is contained in two files (KERNEL and SYSTEM) and then we delete the .tar file and folders we extracted those from.
Posts by chewitt
-
-
I'm fairly sure that Google won't remove widevine support from or kill updates to ChromeOS, so that route will always be open. It would be a lot easier to redistribute the extracted files as-is, which is permissible, but by doing so you accept Google's license terms. To say they favour Google is rather a large understatement, and punitive is probably a good word for them.
The libs allow Kodi to access DRM protected content by pretending to be a web browser.
-
Probably best to ask in the Plex add-on thread in the Kodi forums, or start a thread on JSON-RPC things; it's nothing specific to LE.
-
The primary goal for the initial launch codebase on RPi4 (Linux 4.19) is to not regress/break anything. All development focussed on pushing forwards to better performance and new features like HDR is focussed on newer kernels and GBM/V4L2. This is currently based on Linux 5.4 and we are close to switching LE master branch (will be LE10 in the future) testing to this codebase. Tearing has been resolved in the future codebase for some time.
-
IIRC sftp support was removed from core and reimplemented as an add-on.
-
I'm pretty sure, that's a copy and paste from a release nearly 6 months ago, isn't it
CvH you've been rumbled
-
Google only publishes 32-bit libwidevine for Linux/ARM use and even that has to be extracted from a 3GB ChromeOS update image. There is no 64-bit lib that's ever been found, and we haven't ever managed to use the 32-bit lib in 64-bit userspace via compat tools. So we can either build images with 32-bit userspace and facilitatte access to Amazon, Netflix and a number of other DRM oriented streaaming platforms, or we can give a marginally better performing 64-bit userspace without them. As much as DRM sucks balls, it's a fact of life in the world of legal streaming, and we (and Kodi) would prefer to encourage use of legal streaming services than create yet-another obstacle to encourage use of pirate services.
-
OpenWRT supports WireGuard, and i'd expect most the other replacement router firmwares will too.
-
In theory there are compat layer things but I haven't seen anyone report success with them. So we're either doing something wrong but will be stuck until someone points out the secret formula for success, or we're right in thinking it's not possible.
-
LE doesn't need them or use them so I have no experience with them, so no opinion on them.
-
-
Login to what?
-
Rainbow screen normally means wrong image (e.g. RPPi2 on RPi0).
-
The LE settings add-on was authored in 2013 long before systemd was being used seriously in the distro so it doesn't follow mask/unmask conventions for controlling service start/stop; instead there are boot-time scripts that read presence (or not) of files and even the read the content to determine how some things start. There's an underlying theme but each service may have quirks so you'll need to ask more-specific questions to get a specific answer for a specific service. The settings add-on also controls all the networking bits via connman over d-bus; you cannot modify networking by editing files unless you stop connman, edit, then restart, else connman does not know about the changes and will overwrite things. LE settings and how some of the boot-time things are done are long overdue a rethink and rewrite, but that requires someone to volunteer to do it, and "if it works, don't fix it" often applies
-
mglae some early testing is positive. I've enabled systemd-time-wait-sync and added time-sync.target to "After" in wireguard.service. If we see a few more positive reports I'll push some changes.
-
genidy.m please do not cross-post the same information to multiple threads. If you make one post it will be seen by the developers and mods. Multi-posting is annoying and will normally decrease (not increase) the chances of someone taking an interest in your problem.
-
One of the challenges with RPi boards is there is no power-off button. So 99.9999% of the time you get away with a hard power pull, and once in a while you don't. It's imposssible to diagnose the problem from that screenshot, so you probably need to nuke LE using the noobs boot manager and reinstall.
-
It would be nice to do this but Kodi doesn't currently have API methods that would allow it to be done, and it's programatticaly complicated as Kodi supported languages has a different list of things to Kodi input settings which is different to OS locales which is different to Wireless RegDom options so there's no neat/tidy 1:1 mapping of things. It's not impossible to improve, but so far nobody on staff (which includes plenty of Germans) has ever volunteered to tackle the task
