Try setting SSHD_DISABLE_PW_AUTH="true" in /storage/.cache/services/sshd.conf and run "systemctl restart sshd.service" to bounce the daemon and reload the new config.
Posts by chewitt
-
-
Retest with a current milhouse build (assuming this is a 'Generic' install if it has USB3) which runs newer everything.
-
IIRC library auto-update can be run nightly or on startup, but there are kodi-send commands that could be used with systemd .power services to run a command on wake. Subtitle options changed between Jarvis and Krypton so you will need to adjust them.
-
This forum has nothing to do with Android.
-
I apologize in advance if this is a silly question, but are there plans to eventually merge them into LibreELEC down the road?
Apology accepted. Yes.
-
There are no publicly released images for LE on the shield so that can be eliminated. Have a look at MrChromebox.tech for instructions on how to install LE to the Chromebox.
-
I got if from my original Android firmware
Android device tree files work on Android not Linux. On an LE 3.14 kernel they will be similar, but they are not interchangeable.
-
The reasoning still stands. On most devices time to wake from hibernate will be slower than a clean boot. Also consider that 85%+ of our installed base has hardware that lacks the power management functions to hibernate. You're welcome to self-build and experiment for your own needs but it's not even remotely on our roadmap to resurrect hibernation.
-
SSH in and "rm -rf /storage/.kodi/addons/blah" where blah is the name of the addon
-
CGarces I've not been tracking the status/state of RT drivers for some time. If adding the missing ID works please send a PR
-
Intel and RaspPi are the only two manufacturers who will get reliable Kodi support in the future.
I look forward to making you eat your hat in the future. Seriously
-
I wouldn't expect a mainline release for K18 (LE9.0) at this time.
-
I'm already running an LE image with K18 and a Linux 4.17.3 kernel on S905+ devices but the codebase needs to hit some milestones before we invite public testing and feedback. The core OS is solid but audio/video are still in a proof-of-concept state. LE is orchestrating the current activity on Amlogic mainline audio/video things and one of our extended team also contributes to Armbian; so once things are useable Armbian will see some updates too.
-
You can install Kodi add-ons that contain binary apps (as network-tools does) but there is no apt-get or equivalent in the OS. So you either add things to extend an existing add-on package (and then submit changes to our git repo.. or not) or you create new ones (and submit them to our git repo.. or not). I think the questions you're asking show you're not familiar with how LE is build/packaged, so before you run away with ideas of reconfiguring LE to be OpenWRT go find the "self-build" instructions in the wiki and compile an image. There are no instructions on how to add more packages to the OS, but there is a ton of "prior art" in our git repo. From past experience; if people have the skills and knowledge to succeed in that kind of task .. that's all they need to get started.
-
LibreELEC.tv/package.mk at master · LibreELEC/LibreELEC.tv · GitHub
^ that's what it contains. Devs generally have no objections to adding other binaries to the tools package, but it's up to the people that want something added to test and submit the required/desired changes. As a broad rule we'd also want to focus on things that have a use case beyond one person. I think this is the first post to mention RADIUS in the 7+ years I've been hanging around LE/OE etc.
I'll also pass the general comment that if you want a router/firewall distro .. use a router/firewall distro. LE is neither.
-
Kodi has no limit on the number of sources you can have so you should expect to have more than one folder for music to manage different scraper requirements. In other words; the correct answer is in post #2.
-
As v8.2.5 is very likely to be the final release of the Krypton builds
No "is very likely" .. it is the final Krypton release.
-
SSH works fine, but 99% of the filesystem is readonly so you cannot edit things in /etc and if-up.d doesn't exist because we use connmand as the connection manager. You can use "route add" via /storage/.config/autostart.sh which is run at boot time (before networking starts so you need to background and sleep the additions).
No idea about BT modules, but you should consider that C2 is currently stuck on a shitty 3.14 bsp kernel so BT support is well out of date.
