It should be exactly the same as there have been no changes to that part of the OS
Posts by chewitt
-
-
All current builds are using Linux 4.4.6, the imx6 project and various experimental things may be on older kernels. What's the reason for asking?
-
CvH: there's no force-refresh in Jarvis .. progress
-
-
Orange Pi? .. if yes, one of the devs recently acquired a board, but this is AllWinner stuff with poor upstream support for drivers/kernel things so unless it just happens to work at the first attempt it will be a very low priority for investigation and development.
-
v6.90.004 will be pushed as a .tar update (sometime in the next 24 hours) to correct things in the settings app and v6.90.005 will re-test .img.gz update. It's working fine here when testing fixes this morning
-
It was already done but the commit hadn't been merged. Leafy niceness will appear in 6.90.004
-
which hardware/device and build are you using?
-
Having struggled with various attempts that nearly-but-not-quite worked I had the "I wonder if someone wrote an online .htaccess converter?" thought and 30 seconds later htaccess to nginx converter gave me a working nginx config
-
The Chromium browser created by lrusak will be migrated to our addon repo soon (another item on a long to-do list) but although this installed as a Kodi add-on the app runs in the OS outside of Kodi (not in the GUI).
-
From experience; the number of people that label a large USB drive "Storage" is quite high
-
I'm guessing aarch64 as this is the name of the branch lrusak had been working on prior to the fork:
Once he gets back from a small vacation rebasing against LE is on his/our todo list. At the moment the branch looks to be safely behind the 350+ untested changes that OE shovelled into master a few days before 7.0b1.
-
It's better practice to use disk=UUID=<string> to mount /storage from cmdline.txt in case you ever connect another USB drive and reboot to discover it claimed /dev/sda instead of the SSD drive.
-
Do you really need to custom build? .. You get stronger security (not just obscurity) and easier access if you add your SSH public key to authorized_hosts and disable password auth, and you can also set auto-update to manual and disable update notifications.
I'll have a look at replicating OE's behaviour with some nginx redirect fu on the webserver. Some RTFM is required
-
There are several people in the community looking at the Odroid C2 including people on LE staff and currently we're working to ensure people are collaborating together instead of working in isolation. One of our staff has LE "running" on C2 hardware but Kodi segfaults frequently so it's still early days. If you're a user looking to purchase a C2 for Kodi use; it's a nice spec but isn't something we can recommend yet. If you're a developer who'd like to help us tackle the C2 please send myself and/or lrusak a PM so we can loop you into our efforts.
-
If you have USB 2.0 ports, plug the USB there. Also look in the BIOS for legacy boot options and experiment there.
-
This is on a list of things to investigate.
-
kobrawerde: the Generic image for LE contains multiple nvidia drivers (352.xx and 304.xx) with active driver selection based on the PCI bus ID's of the GPU so there's no need for a separate "Legacy" image.
Skype isn't likely to happen as it's distributed as a pre-compiled binary that expects a bunch of conventional Linux desktop capabilities to be available and LE (as with OE) has the bare minimum needed to run Kodi as a full-screen app. We could probably back-fill some of the dependencies needed to run it, but you'd still need to stop Kodi to see Skype on-screen (same as the Chrome browser situation today) and then restart Kodi when done. At the end of the day it's a clunky user experience. If Skype is essential you'd be better off with a conventional Linux desktop distro.
Please explain what the use-case and scenario for a webcam is?