lanefu

thank you! merged!

Or I guess Balbes support is free and easy. Note this is balbes and not official support status

for current use `AUFS=no` and it should build.. ran into that yesterday

Hi Judy, There's a lot of work involved in adding a device to Armbian. In your case, a new product without mainline linux support, it's an enormous amount of labor. It's unlikely there will be any community members willing to do the engineering required for free. Are you looking for a paid engagement? Are there kernel source code and device tree source code published and available for this product? https://docs.armbian.com/User-Guide_FAQ/#where-do-i-ship-a-board-so-that-armbian-will-add-support

There's a service called lightdm that you'll need to look at. It launches X and the GUI login. Hope that helps

I'm not familiar with that. What causes and issue with the wifi and USB 3?

You're probably going to need to be a little more hands on with the tool you choose. I like borg and borgmatic.

Hi great question. Def can be confusing. We're working to be more clear. GitHub issues (NOT PRs) are meant to be specific to the Armbian build engine and not specific to devices. Raise device issues on forum for conversation and hopefully find the attention of a maintainer. (Part of reason we do it on forum is it creates too much noise on GitHub for such a small team of devs) If it's an issue a maintainer or armbian developer thinks it needs to be prioritized, they will add to our Jira For those that don't like posting on forum anybody can open a draft PR with a proposed solution and explanation of what's being solved in GitHub

Yeah that was my experience with libgpiod a year or 2 ago. No pull-ups etc. It's not ready for prime use. Sysfs gpio access is the most consistent method to deal with gpio accross different devices. And I'll gladly take it over 20 forks of wiring pi (which truly is deprecated in a much more literal sense) for background Even Adafruit jumped on the bandwagon libgpiod when it was announced but they quickly backed off quietly once the reality hit that it wasn't ready for their core customer base. Deprecated in Kernel land doesn't meant stop using immediately, it means don't extend and start preparing/be aware for the (long-term) future

This functionality existed in our pervious stable kernel 5.10.y and should absolutely continue to be supported. It was a breaking change that should not have happened. lane

Ha yeah it was extremely deprecated lol. I was in a "there has to be a markdown plugin" mode scouring the interweb and saw that. On that note I think I did toggle the plain text paste flag off. So copying rendered markdown into the editor may work. Anyway the editor seems to be a whole seperate body of work independent from Invision other than it'd what they use. Sounds like Invision actually has their own upgrading to do from "v4" to "v5"

is this post meant to be in this thread?

That's beyond the feature-scope of Armbian. And yes a great feature on diet-pi, which makes a very nice appliance experience for the user..... part of it's appliciance-ification approach to config management is also what lets it back up so nicely.

oh lord, really? you use it?

All great points. Oneshot seems appropriate. I don't think there's an outstanding technical reason that would prevent us from changing it. Feel free to open a draft pull request as your developing. would ask that this piece be a separate PR from one shot service changes discussed.