Hi all; today 6.1.0-beta1 has been made available in the FRS
https://sourceforge.net/projects/leaf/files/Bering-uClibc/6.1.0-beta1/ LEAF Bering-uClibc 6.1.0 will be based on uClibc-ng 1.0.25, gcc 5.4.0, kernel 4.9, perl 5.26.0 and busybox 1.27. The full blown libiconv package (approx 650kb) has been replaced with uClibc- ng implementation of libiconv (adding a few kb to initrd). initrd merged root.lrp and config.lrp into initrd.lrp In addition to Raspberry1 support for Raspberry3 has been added. The Raspberry3 tarball may also work with Raspberry Pi2, though this hasn't been tested. Also it provides numerous packages updated to latest upstream versions and feature improvements (e.g. shorewall, tor, bind, openvpn, added ldap support to dhcpd). Also new packages has been added: libndp - a library which provides a wrapper for IPv6 Neighbor Discovery Protocol and a tool named ndptool for sending and receiving NDP messages libaio - Library for doing asynchronous I/O libtirpc - The libtirpc package contains libraries that support programs that use the Remote Procedure Call (RPC) API. rpcbind - The rpcbind program is a replacement for portmap. It is required for import or export of Network File System (NFS) shared directories. sqlite - SQLite is a self-contained, high-reliability, embedded, full- featured, public-domain, SQL database engine; required for NFSv4 support. ca-certificates - ca-certificates provides a list of Certification Authorities. It is based on the Debian package, which itself provides the ones from Mozilla dehydrated - ACME client implementation for Let's Encrypt (https://letsencrypt.org/) The default http[s] daemon mini_httpd[s] has been replaced with lighttpd. Therefor lighttpd has been adjusted to run webconf. A note here: by default lighttpd/webconf are installed without ssl support. To add ssl support you need to create your own certificates in /etc/ssl/private, change the lighttpd configuration and save the configuration. A short recipe is given, if you run "help lighttpd" on the commandline. Using lighttpd with ssl is flexible, so you are not bound to the default name "lighttpd.pem", you may create your keys elsewhere, you may even try to use letsencrypt with the dehydrated package to create a key supported by your browser out-of-the box. (If someone works out how to use that, a documentation for the Bering-uClib User Guide is welcome :)) Speaking about the User Guide, there are still gaps in the 6.1 version https://bering-uclibc.zetam.org/wiki/Bering-uClibc_6.x_-_User_Guide if you are capable to fill those or like to add a new chapter, let us know, any help is welcome. For more information see about the changes for LEAF Bering-uClibc 6.1 : https://bering-uclibc.zetam.org/wiki/Bering-uClibc_6.1.x_-_Changelog Feedback and suggestions are welcome. thx for your attention kp ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot ------------------------------------------------------------------------ leaf-user mailing list: leaf-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-user Support Request -- http://leaf-project.org/
