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?
Mario S. - good spotting, will be solved when samba: change server name to LibreELEC by chewitt · Pull Request #50 · LibreELEC/LibreELEC.tv · GitHub is merged
There are no committed plans beyond RPi (which are already supported) and we are not going to suddenly add more projects/devices into our github repo. There is keen interest among the LE team (and in community people we're starting to make friends with) to work better together, but it's very early days and there is nothing concrete to talk about yet, and if we do figure out how to absorb some of the above in the future it will be done slowly to ensure the right result.
Auto-update is already in-place but there is currently nothing to auto-update to. There will be news about releases and process soon
NB: In the long-term LE will include some changes to ease the process of major version updating for users, but the problem here is not OE/LE or Kodi itself but the add-ons users install. People like myself who run deliberately simple configurations would have no issue (my current main box has updated from OE 2.0 > LE 7.0 without issues) but those with complex DVB and Library arrangements would be rightfully pissed if an auto-update wrecked things (and it does happen) so our overall position on major version changes will not be wildly different from OE or any other Kodi-using distro.
Hello,Why using github for issue management and feature requests?
It integrates well with the PRs and the history.
"Issues" are not enabled to prevent GitHub becoming a general dumping ground for poorly submitted user bug reports. We'd prefer to keep that noise in the forums. This may change if/as/when GitHub tweaks how their Issues feature works and as the LE team comes up to full operating speed.
btw, check your email
OpenELEC dropped 32bit support in version 6.What about adding it back?
What is your stance about retro compatibility? Are you going to drop features to maintain a small codebase like OE does, or are you going to take a different path?
At the time OE dropped i386 there were ~7.5k active i386 users, but only ~1.5k had a true 32-bit only CPU (the settings addon was tweaked to collect anonymous stats on this) so the majority could (and most since did) update to a 64-bit build. It was something like 0.003% of the active userbase at the time. It would be an even smaller percentage today.
OE has never been a great distro for recycling old hardware with and LE has no intentions of being different. We're not going to rush back and fill the tiny i386 niche with an official build. We will be thoughtful of long-term direction to avoid bloat when making any changes, but overall, and to quote Dr. Spock: "the needs of the many outweigh the needs of the few"
That said. Once we've found our operating rhythm and I have some free time I will be rebasing patches and releasing a private LibreELEC 7.0 (Jarvis) community build for the mk1 AppleTV (as I have done in the past under OE) and since this is an i386 build with CrystalHD support it will be relatively straightforward for someone else in the community to figure out the remaining changes needed to create a 32-bit "Generic" image from the same github branch. If someone does the work I'd be happy to merge their PR's so others can self-build their own i386 images.
we rebranded *everything* so it's root/libreelec not root/openelec
It was "a build made by Milhouse" (and LE, so v16) but not "a Milhouse build" (which would be v17) so we can see the confusion. Some official builds will be along shortly ..not built by Milhouse, and he plans to resume his Milhouse builds (via Kodi forums as usual). Are we all clear (as mud) now? 
I now have installed the LE plus an addon to update Openelec
This addon have the Millhouse and the Openelec updates >
How to update LE if there are newer or dev updates
Once official alpha/beta builds start they will be versioned and the auto-update system can be used to flag new builds. If you're using Leopold's updater add-on the temp fix is to scrape Index of /builds/stable/ where he's posting things. Official builds should be along soon-ish
Number schemes were discussed among the team and while tracking Kodi versions is good (as it highlights whats inside) it also makes us beholden to the Kodi versioning system and could equally cause confusion. We also need to consider people cross-grading from OE and trying to figure out what we are vs. OE. The compromise reached is the format "LibreELEC 7.0 (Jarvis)" ..which respects heritage (we're mature, not v1.0) allows cross-compairson to OE, avoids having two distinct sets of numbers in the name, but still highlights what's inside. So on anything official like release announcements and file download lists - that's the format you should see.
sudo apt-get install libxml-parser-perl
that should get things going. Hi-Silicon stuff is not supported (and not even remotely on anyone's radar).
WeTek (who are good folks) have not negatively influenced the OE release schedule. They're as much in the dark as everyone else
git clone https://github.com/LibreELEC/LibreELEC.tv LibreELEC.tv
cd LibreELEC.tv
PROJECT=WeTek_Play ARCH=arm make image something like that will do it