Oryx Linux Re-Launch02 May 2017
This is a quick update for anyone who's read the old blog posts or looked at Oryx during the 2016 to early 2017 period.
Oryx Linux began as an idea I had back in May/June 2016 to experiment with some new ideas in how to deliver embedded Linux® systems. Initially the focus was on using Oryx as a playground to try out these ideas and there was no short-term intention of it being used as a basis for real-world embedded Linux deployments. During this phase I tried out options such as using musl libc instead of glibc, using toybox to provide base system utilities instead of busybox, using clang as the system compiler where possible and even with integrating an alternative init system into OpenEmbedded.
This phase of Oryx development was a good way of exploring these ideas and testing the waters to see what was possible, but it ultimately wasn't very satisfying. As Togán Labs began to form in early 2017 we saw an opportunity to do something more with Oryx. Instead of being a rough-and-ready experimental playground in which to try out software which isn't yet production ready, Oryx would focus on integrating those new ideas which are production ready. The aim is now to provide a deployable embedded Linux solution which incorporates up-to-date best practices within the industry.
After this change of direction for Oryx, some old decisions had to be re-thought. The decision on whether to use toybox instead of busybox is now postponed until after toybox has reached a v1.0 release. The system compiler will remain gcc for the time being. However, we will still be using musl libc as the default for Oryx as this is already a widely tested and deployed C library implementation. The ever-controversial decision of which init system to use will also be addressed in the coming months.
Finally, Oryx is now a Togán Labs Ltd project and so any queries should be sent to our new support email address, firstname.lastname@example.org, instead of my personal email address.