<p dir="ltr">On May 10, 2016 7:30 PM, "Peter Robinson" <<a href="mailto:pbrobinson@gmail.com">pbrobinson@gmail.com</a>> wrote:<br>
><br>
> On Tue, May 10, 2016 at 9:39 PM, Adam Holt <<a href="mailto:holt@laptop.org">holt@laptop.org</a>> wrote:<br>
> > On May 10, 2016 3:21 PM, "Peter Robinson" <<a href="mailto:pbrobinson@gmail.com">pbrobinson@gmail.com</a>> wrote:<br>
> >><br>
> >> We do have initial pine64 support, I plan to improve it more for GA and<br>
> >> have a disk image for use.<br>
> ><br>
> > Great News!<br>
> ><br>
> > Tangentially: are there opinions emerging on the physical ruggedizability of<br>
> > 2GB Pine64 v. 1GB RPi3 (incl WiFi) for developing world education, and harsh<br>
> > environmental/ergonomic conditions, as more people start banging on both?<br>
><br>
> I'm sure I've said it before, it's not high quality. My alpha board<br>
> arrived bent (still works somehow) but the hackaday review [1] sums up<br>
> my opinion quite well. This isn't a robust device, and with up to 2Gb<br>
> of RAM there's a lot more ARMv7 devices that offer better value for<br>
> money. At a max of 2Gb of RAM a 64 bit chip offers absolutely ZERO<br>
> advantage and it's built for a price and I'm sorry but "harsh<br>
> environment" is not anywhere in that. Honestly a BeagleBone would do<br>
> better and has much better build and likely better performance for not<br>
> much more price (yes, I do class double the price in this class as not<br>
> much more)<br>
><br>
> [1] <a href="http://hackaday.com/2016/04/21/pine64-the-un-review/">http://hackaday.com/2016/04/21/pine64-the-un-review/</a></p>
<p dir="ltr">Fascinating, Thanks!</p>
<p dir="ltr">(Since I'm working with Haitians who cannot pay double the $35 price of RPi3...we'll be looking more seriously at ruggedizing the official Raspberry Pi 3 for now...and it's unofficial community support perhaps most important.)</p>
<p dir="ltr">Knowing we cannot possibly prevent all failures, but rather hoping that field production use today...affects RPi4/5/6 as a family, increasingly growing up from rich-world gadgeteers' basements........to globally-relevant nanoservers operationalizable for a billion people who demand to be relevant.....even IF they will never in their lifetimes get a $15/hour minimum wage :-/</p>
<p dir="ltr">> >> Peter<br>
> >><br>
> >> On 10 May 2016 18:44, "Adam Holt" <<a href="mailto:holt@laptop.org">holt@laptop.org</a>> wrote:<br>
> >>><br>
> >>> Not sure the 64-bit implications of this for RPi3 and Pine64, but FYI.<br>
> >>><br>
> >>> ---------- Forwarded message ----------<br>
> >>> From: "Peter Robinson" <<a href="mailto:pbrobinson@gmail.com">pbrobinson@gmail.com</a>><br>
> >>> Date: May 10, 2016 1:34 PM<br>
> >>> Subject: Announcing the release of Fedora 24 Beta for aarch64!<br>
> >>> To: <<a href="mailto:arm@lists.fedoraproject.org">arm@lists.fedoraproject.org</a>>,<br>
> >>> <<a href="mailto:devel-announce@lists.fedoraproject.org">devel-announce@lists.fedoraproject.org</a>>,<br>
> >>> <<a href="mailto:announce@lists.fedoraproject.org">announce@lists.fedoraproject.org</a>>, <<a href="mailto:secondary@lists.fedoraproject.org">secondary@lists.fedoraproject.org</a>><br>
> >>> Cc:<br>
> >>><br>
> >>>> The Fedora 24 Beta for aarch64 is here, on schedule for our planned June<br>
> >>>> final<br>
> >>>> release. For Beta we have added Cloud and Docker base images.<br>
> >>>> Download the prerelease from our Get Fedora site:<br>
> >>>><br>
> >>>> - Get Fedora 24 Beta Server: make use of the very latest server-based<br>
> >>>> technologies available in the open source community<br>
> >>>><br>
> >>>> <a href="https://dl.fedoraproject.org/pub/fedora-secondary/releases/test/24_Beta/Server/aarch64/">https://dl.fedoraproject.org/pub/fedora-secondary/releases/test/24_Beta/Server/aarch64/</a><br>
> >>>><br>
> >>>> - Get Fedora 24 Beta Cloud: build scale-out computing and utilize the<br>
> >>>> next<br>
> >>>> generation of container deployment technology<br>
> >>>><br>
> >>>> <a href="https://dl.fedoraproject.org/pub/fedora-secondary/releases/test/24_Beta/CloudImages/aarch64/">https://dl.fedoraproject.org/pub/fedora-secondary/releases/test/24_Beta/CloudImages/aarch64/</a><br>
> >>>><br>
> >>>> <a href="https://dl.fedoraproject.org/pub/fedora-secondary/releases/test/24_Beta/Docker/aarch64/images/">https://dl.fedoraproject.org/pub/fedora-secondary/releases/test/24_Beta/Docker/aarch64/images/</a><br>
> >>>><br>
> >>>> What is the Beta release?<br>
> >>>> -------------------------<br>
> >>>><br>
> >>>> The Beta release contains all the exciting features of Fedora 24's<br>
> >>>> editions in a form that anyone can help test. This testing, guided by<br>
> >>>> the Fedora QA team, helps us target and identify bugs from the Alpha<br>
> >>>> version. When most of these bugs are fixed, we make a Beta release<br>
> >>>> available. A Beta release is code-complete and bears a very strong<br>
> >>>> resemblance to the third and final release. The final release of Fedora<br>
> >>>> 24 is expected in June. We need your help to make Fedora 24 the best<br>
> >>>> yet. Please take some time to download and try out the Beta and make<br>
> >>>> sure the things that are important to you are working. If you find a<br>
> >>>> bug, please report it – every bug you uncover is a chance to improve the<br>
> >>>> experience for millions of Fedora users worldwide. This is a great<br>
> >>>> opportunity for non-programmers to contribute back to fedora. Together,<br>
> >>>> we can make Fedora rock-solid. We have a culture of adding new features<br>
> >>>> to software and pushing fixes to the upstream developers at the same<br>
> >>>> time. This means your feedback will help improve not only Fedora but<br>
> >>>> Linux and free software on the whole.<br>
> >>>><br>
> >>>> - <<a href="https://fedoraproject.org/wiki/Releases/24/Schedule">https://fedoraproject.org/wiki/Releases/24/Schedule</a>><br>
> >>>> - <<a href="https://fedoraproject.org/wiki/How_to_file_a_bug_report">https://fedoraproject.org/wiki/How_to_file_a_bug_report</a>><br>
> >>>><br>
> >>>> Fedora-Wide Changes<br>
> >>>> -------------------<br>
> >>>><br>
> >>>> Under the hood, glibc has moved to 2.23. This update includes better<br>
> >>>> performance, increased security, bugfixes, improvements to POSIX<br>
> >>>> compliance, and additional locales. The new library is backwards<br>
> >>>> compatible with the version of glibc that was shipped in Fedora 23.<br>
> >>>> We've also updated the system compiler to GCC 6 and rebuilt all of our<br>
> >>>> packages with it, providing greater code optimization and improved<br>
> >>>> program error catching.<br>
> >>>><br>
> >>>> Server<br>
> >>>> ------<br>
> >>>><br>
> >>>> Fedora 24 beta server edition has also been more streamlined.<br>
> >>>> Unnecessary<br>
> >>>> packages were removed and the installer has a smaller footprint. FreeIPA<br>
> >>>> 4.3, an integrated security information management solution is now<br>
> >>>> included. The installation of replicas is streamlined by adding a<br>
> >>>> replica promotion method for new installs. A new topology plugin has<br>
> >>>> also been added to this version of FreeIPA that automatically manages<br>
> >>>> new replication segment creation. An effective replica topology<br>
> >>>> visualization tool is now available in the webUI.<br>
> >>>><br>
> >>>> Cloud<br>
> >>>> -----<br>
> >>>><br>
> >>>> We are working hard to make Fedora the best platform for containerized<br>
> >>>> applications, from base Fedora container images to a full-featured<br>
> >>>> platform as a service to run and manage them. To meet this goal, we are<br>
> >>>> packaging OpenShift Origin so it is easy to deploy. OpenShift Origin is<br>
> >>>> a distribution of Kubernetes, a container cluster manager from Google.<br>
> >>>> It is optimized for enterprise application development and deployment.<br>
> >>>> Origin makes it easy for developers to get started building applications<br>
> >>>> in containers and for operators to manage them.<br>
> >>>><br>
> >>>> Issues and Details<br>
> >>>> ------------------<br>
> >>>><br>
> >>>> This is a Beta release. As such, we expect that you may encounter bugs<br>
> >>>> or missing features. To report issues encountered during testing,<br>
> >>>> contact the Fedora QA team via the mailing list or in #fedora-qa on<br>
> >>>> Freenode. As testing progresses, common issues are tracked on the Common<br>
> >>>> F24 Bugs page.<br>
> >>>><br>
> >>>> - <<a href="https://fedoraproject.org/wiki/Common_F24_bugs">https://fedoraproject.org/wiki/Common_F24_bugs</a>><br>
> >>>><br>
> >>>> For tips on reporting a bug effectively, read "how to file a bug<br>
> >>>> report."<br>
> >>>><br>
> >>>> - <<a href="https://fedoraproject.org/wiki/How_to_file_a_bug_report">https://fedoraproject.org/wiki/How_to_file_a_bug_report</a>><br>
> >>>><br>
> >>>> Release Schedule<br>
> >>>> ----------------<br>
> >>>><br>
> >>>> The full release schedule is available on the Fedora wiki:<br>
> >>>><br>
> >>>> - <<a href="https://fedoraproject.org/wiki/Releases/24/Schedule">https://fedoraproject.org/wiki/Releases/24/Schedule</a>><br>
> >>>><br>
> >>>> The current schedule calls for a beta release towards the beginning of<br>
> >>>> May, and the final release in early June. Be aware that these dates are<br>
> >>>> development targets. Some projects release on a set date regardless of<br>
> >>>> feature completeness or bugs; others wait until certain thresholds for<br>
> >>>> functionality or testing are met. Fedora uses a hybrid model, with<br>
> >>>> milestones subject to adjustment. This allows us to make releases with<br>
> >>>> new features and newly-integrated and updated upstream software while<br>
> >>>> also retaining high quality.<br>
> >>>> --<br>
> >>>> announce mailing list<br>
> >>>> <a href="mailto:announce@lists.fedoraproject.org">announce@lists.fedoraproject.org</a><br>
> >>>><br>
> >>>> <a href="http://lists.fedoraproject.org/admin/lists/announce@lists.fedoraproject.org">http://lists.fedoraproject.org/admin/lists/announce@lists.fedoraproject.org</a><br>
> >>><br>
> >>><br>
> >>> _______________________________________________<br>
> >>> Server-devel mailing list<br>
> >>> <a href="mailto:Server-devel@lists.laptop.org">Server-devel@lists.laptop.org</a><br>
> >>> <a href="http://lists.laptop.org/listinfo/server-devel">http://lists.laptop.org/listinfo/server-devel</a><br>
> >>><br>
> ><br>
> ><br>
> > _______________________________________________<br>
> > Server-devel mailing list<br>
> > <a href="mailto:Server-devel@lists.laptop.org">Server-devel@lists.laptop.org</a><br>
> > <a href="http://lists.laptop.org/listinfo/server-devel">http://lists.laptop.org/listinfo/server-devel</a><br>
> ><br>
</p>