-----Original Message-----
From: Andreas Färber
Salut Jimmy, Hallo Andreas,
I am awfully sorry for asking questions. The idea was not to redo tests if already done before. I am re-installing this ISO : openSUSE-Leap-15.1-DVD-aarch64-Build458.3-Media.iso on QEMU. I have also ordered 8 GB RAM. I will also install WireGuard aarch64 and pi-hole. The pre requisite are governed by the hardware and this is not my choice. I will peruse the links too, thanks Andreas. It has been two years since I went to FOSSDEM and I am just 3 hours' drive to Brussels. Sadly, many projects are keeping me at bay. It's also a good idea to follow what Michal K. and openSUSE-kernel are doing rather than bothering you with same. NUI was Novell Users International until about 7 years ago. It has been 19 years' service as volunteers as well. It's not a website but it is all about evangelizing. We have roughly 15 events per year on openSUSE and SUSE.
If you have a spare system that you can reinstall if needed, you can try https://build.opensuse.org/project/show/Kernel:linux-next today, at your own risk; CONFIG_WIREGUARD appears to be enabled as module. It gets updated automatically and is not QA'ed. We do have spare boxes, and it's more gratifying to do it the hard way, system > software.opensuse.org and/or editor's ftp etc. We will need to install modules manually one day or another. So the earlier to get acquainted with....
Sorry again for sharing my problems. Sincerely, Dr. Jimmy Pierre President Network Users institute https://nui.fr Am 02.02.20 um 14:09 schrieb jimmypierre.rouen.france@gmail.com:
Once final v5.6 is released and built in Kernel:HEAD, it'll be submitted to Kernel:stable and then openSUSE:Factory and will ultimately appear in Tumbleweed. Great! Allow me to sort of rephrase my question. As far as you know does WireGuard work fine on openSUSE Arm please?
I do not know! To me it is just one out of dozens of Kconfig options that'll be new in 5.6. To get an idea of what I've been talking about in the previous answer, see here my last arm64 update for 5.5 cycle: https://github.com/openSUSE/kernel-source/commit/4e170862d6ded97cf6461516281... From my local linux-next based development trees I know that the option is available for both 32-bit arm and 64-bit arm64. But I have no clue what your favorite option does, nor how to test it, and on most new boards that I spend my time on enabling I don't even have Ethernet drivers yet.
And when kernel 5.6 will be released in April or so, WireGuard will be part natively, will openSUSE Arm support same? It's aarch64 the target as I believe that x64/Tumbleweed is taken care of.
To me, openSUSE Arm is Tumbleweed, and I explained the process for that. Dunno what you mean with taken care of. Please re-read my full answer: I will choose whatever is chosen for x86_64 and the other openSUSE architectures. So if you want Michal K. to look into his crystal ball, you'll need to ask on opensuse-kernel list. If you're asking whether I'll be quick enough in updating the configs, that I can't guarantee, -rc7 was fairly late this cycle, and armv6hl/armv7hl are still unfinished. If everything were great with me, I'd be at FOSDEM now, not answering emails... At this stage without -rc1 this is all very hypothetical still. The option might get reverted upstream, for instance, if there's problems.
I run NUI.fr (basically a LUG, Computer Club) since 2001 and before telling my guys what we will be working on as we do have visitors and if they see us "fiddling", they will lose interest and negatively "advertise" our activities.
Whatever website you run doesn't change our workflows nor that this is all driven by volunteers in their spare time. You'll need to be patient and do your own testing before you try to show it off wherever. If you have a spare system that you can reinstall if needed, you can try https://build.opensuse.org/project/show/Kernel:linux-next today, at your own risk; CONFIG_WIREGUARD appears to be enabled as module. It gets updated automatically and is not QA'ed. You'll need to figure out whether any userspace packages need to be added or updated to make use of the kernel option (e.g., iproute2 or similar NetLink based tools). I could imagine that if you expect YaST support for such new technologies, you might need to contribute it yourself. The good thing is, with OBS you can easily show your members how to update and test branched packages for that. Regards, Andreas -- SUSE Software Solutions Germany GmbH Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer HRB 36809 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org