Werner

Everything is a bit slower when running through virtualization. Depending on the task more or less. It is kind an insurance as the build script messes with the system like stated with loop devices, apt and so on.

May you share your working configuration as PR to armbian-build on Github? H6 is still WIP and I guess the cutback that comes with it (hwaddress) is justifiable ... and it is still development, right?

May you create a (hidden) testing forums for this feature, just to get a look'n'feel for it?

By the way it is recommended to create a building environment encapsulated in a VM and not

I know. Though I do not think that the similarity of what the project is all about is important in this case. All have to deal with development, bug reports, user support and off-topic in a way or another.

Any open source project will do for comparison I guess. The first thing that came into my mind was Filezilla. I took a quick look and they are using forums for support and Trac for issues. I am not sure how this subdivision works out for them as an end-user you may not know if you actually found a bug or just acting stupid or whatever. In comparison we would divide between build-script (issues/support) and the provided pre-built images (issues/support). The next project was LibreOffice. On their help you can choose between asking a question (about a softwares' function and so on), report a bug and report feedback/enhancements. The last two things are handled by Bugzilla, for questions they are utilizing some kind a forum. So basically the same subdivision Filezilla is using and coming up with the same question as above. Of course these are two randomly chosen open source projects and a quick look only.

Looking decent. "Departments" could be the current breakdown of the current Technical support forums. To say Allwinner A20, Allwinner H2 & H3 and so on... This seems to be free of charge as well so we won't lose anything by just giving it a try.

http://linux-sunxi.org/Linux_mainlining_effort H5 is way better at the moment. If you do not need the additional processor speed the H6 provides go for the H5. Check the support matrix beforehand though.

"...to create less fragmentation" I have to add Interesting. I will take a look at this later this day.

Yes, you are probably right. A bug tracking system would make sense only if it is implemented within the forums properly I guess. Anyway I was just thinking out loud ;). It is hard to find a good solution because everything will have advantages and disadvantages. It is about to find the way with the least amount of criticism.

Yes. Or Debian with the same kernel. Depends on your taste As for myself I prefer Debian as the directly by Debian maintained packages count is way higher than by Ubuntu. Lots of packages on Ubuntu are Universe or Multiverse which means there is no guarantee for support or (even critical) fixes.

I was thinking about a (dedicated) bug tracking system as well, but for new users it might be difficult to get a hang for it. Though besides Github and forums there would exist a 3rd page that needs maintenance... Would be interesting if the user database can be synced between one of these bug tracking systems and the forums so nobody as to re-register. Another that came to my mind was using Github as bug tracker for issues with the provided images. But I think this may have more disadvantages than other alternatives.

Relax. You are just not using proper software for the purpose. I am running PiHole on an OPi Zero in my LAN as well and it runs perfectly fine. Just use an image which features mainline kernel, not legacy (not 3.4.113 to say as it seems there is no need for advanced graphics output, just server activity) and use Debian Stretch or Ubuntu Bionic as operating system.

Agreed. Also these two last posts of mine could be merged. Sorry for that.

Using some kind a bug tracker implementation would be interesting to see how it flows (Bugzilla, Mantis ...). Though when implemented where would be another system where mostly inexperienced users would ran into trouble how to use it.

Yes. In the early days, about linux 4.17 when the first initial support for Allwinner H6 from Armbian came, it was limited to 1,5GHz but I remember a patch for 4.18 which rised the max frequency to 1810MHz and it ran well. I did benchmark without cooling whatsoever and it survived. Over a longer period of time on heavy load I would think about some kind a cooling though,

@martinayotte May you take a look here: https://github.com/EvilOlaf/build/commit/eb4a36885bc63199bbc5aadb2bd220c560af0109#commitcomment-32007637 Is this something known or worth trying?

It is the same SoC so yes, it may suffer from all these issues as well.

Maybe because no one had a need for it yet. You can build your own kernel and edit the config using the build script: https://github.com/armbian/build If you think this might be useful for others feel free to send a PR with the changes to the kernel config so all future builds include this.

Looking decent. Nothing odd so far. As from my experience topics usually are bumped actively during the first days till maybe weeks, but not over month. The situation here might be different though.

Are there that many older topics that getting exhumed? Not sure if possible with Invision without addon, I know that worked in vB years ago but what about simply limiting the number of visible topics by age up to 90 days as default?

I am torn about this. For various you may not be able to generate such a link. Like network issues (you still get the output but not the special link), I/O issues or boot issues.

I think we should not take take that with a pinch of salt just because it says "Issues". Don't get me wrong, I totally get your point, but if the mix of issues with discussions is either here in the forums (just take a look over there) or at Github issues does not make a big difference. At github discussions can be labeled as those at least as every new topic there needs a review in first place. What about this as a compromise between both: - Rename "Armbian build framework" to "Armbian build framework - Discussions" and - create another subforums Armbian build framework - Issues" which redirects to Github At the bottom line there is no perfect solution for this because there are always and always will be users which are either inexperienced, creating topics at the wrong place by accident or are just trolls. Unfortunately there is no other way than cleaning up behind. That's the curse of all forum operators.

Well I'd guess that using prefixes can also be enforced by the system. So you have to choose on topic creation. Agreed. Annoying work. I already did stuff like that many years ago... What about simply redirecting "Armbian build framework" to https://github.com/armbian/build as all stuff regarding the building process, script and so on is discussed (or should be at least) discussed there?

Like. As an alternating suggestion is to merge mainline and legacy kernel forums and use pre-defined thread prefixes like [Legacy] or [Mainline]. Though two problems: I do not know if possible technically as I never managed Invision forums. vBulletin and WBB only. The second issue I see is more generic as especially new users may not know the difference between legacy and mainline. I did not know by myself a year or two before. At the moment no idea how to solve this. Maybe this is not even a problem as big as I may think. Are A64 and H5 stable enough to be removed from development?