FAQ Gitweb performance Download

About Fenrus Linux

Fenrus Linux is likely a little bit unconventional. We're working on Fenrus Linux, because for us, it's fun to tinker with operating systems and the technologies around that. World Domination does not come into the picture at all... in fact, World Domination is a bit boring and so, well, 2008. As a result of this, you'll likely see us make some unexpected technology choices. In addition, we enjoy tinkering with the how of building an operating system, and you'll see us do things in ways that few others are doing in this space.

Who is it for?

To be very blunt about it... Fenrus Linux is for us and people like us. We're developers, and we want to build an OS where we don't have to feel guilty about using it, an OS where developers are the primary target audience. You want a terminal in the default install? So do we. You got it. We're not going to be perfect at this from the start... so let us know how we can make your life as developer easier.

Software update

One of the things where we are not very happy with the status-quo in Linux is around software update. Sure, yum, apt-get and co work, but they're slow and they end up downloading so much data, that it is very unpractical for distros and users to do frequent updates to fix small bugs. After all, who wants to redownload all of LibreOffice just to get one sentence corrected in the French translation. We feel that the lack of an efficient software update is holding Linux OSes back in getting to a higher quality, to listen to their users more.

We presented about the basics of the software update technology that we use in Fenrus Linux at the Linux Plumbers conference in 2012.


We're a small team, and building a Linux OS can be a lot of tedious work. We're focusing a lot on automation in the project, so that we can spend our copious spare time on things where we add value, and not on things that could be done by the mythical 1000 line perl script.

For example, we completely automate the packaging of over 90% of the components that make up the OS. This doesn't give us the Perfect Specfile(tm) that complies with, say, the Fedora packaging guidelines and on which a human spent hours and hours of time polishing and reviewing the specfile. Instead, it gives us a development flow where we get standardized and consistent packaging that works for us.


We like performance. We like good power management. Well who doesn't?

We fundamentally believe that in order to get decent performance and power behavior in an OS, you need to constantly and continously measure the power and performance of this OS, as you're building or improving it.

We also believe that we should be open about what the results of those measurements are, both the good and the bad. To that end, you can see the results of our measurements over time on the performance page of this site. (warnings: lots of graphs, might make your browser a bit slow)

All Debug Information, All The Time

While developing or debugging something on Linux, how often have you gotten frustrated about getting the right debuginfo rpm installed?

No more! In Fenrus Linux, we use a custom Fuse filesystem that will get any and all debug information you need, on demand, right there when you need it.

This is more awesome than it sounds. The "perf" tool not only always has all symbols... it also has the source code for everything, so that you can see the assembly *and* the C code in the "annotate view".
GDB has complete backtraces, including all function arguments, local variable content and source code for everything in the stack frame, and you can single step through everything in the OS, on a full source code level.

Customization and Support services for Fenrus Linux

Contact us for custom services or support for Fenrus Linux Google+