Nitrux are creating an Operating System for everyone
Hi there! Meet Nitrux. Powered by Linux, AppImages, KDE Technologies, and Qt.
This funding campaign has three main objectives:
- Contribute to keeping our online services up and running.
- Allow the developers to hire new talent to work on Nitrux full-time. At the moment, we're a team of 6 people working full-time on the distribution and its projects. To achieve our goals within a reasonable timeframe we need to eventually add more people to the development team.
- Support and help fund other free software and open-source projects that Nitrux relies on.
What we are working on
Nitrux is an operating system based on Linux. Nitrux works without any need for a traditional installation. The operating system as a whole resides in a single file and directory on your device making it easier to organize with your other data. We provide an operating system already preconfigured for the most common tasks, included is a web browser, an office suite, various utilities including a text editor, a file manager, a calculator, music player, video player and drivers for better hardware support, etc.
Nitrux takes the Ubuntu sources and brings it to a whole new level. We have built Nitrux with the goal of not depending on the Debian package manager (dpkg) or its extended set of tools APT (Advanced Packaging Tool) to manage the operating system. In fact, APT is not part of Nitrux anymore.
Nitrux focuses on the use of the AppImage format as the primary method of software distribution for the operating system.
A free and modular front-end framework for developing fast and powerful user experiences.
A set of templated controls and tools based off QQC2 and Kirigami shared among the Maui set of applications. MauiKit helps to quickly build UIs that follow the Maui HIG and bring ready to go tools for different platforms, such as Android and Linux.
- Cross-platform. Components ready to easily use and that work on Android and Linux.
- Convergent. Easily create applications that work in mobile devices and desktop computers.
- Built with Kirigami. MauiKit is built using KDE Kirigami framework and Qt Quick Controls 2.
A new horizon for Linux distributions.
We have aimed to make znx simple and easy. Simple to understand and maintain and easy to use for potential users.
What does it do? znx deploys the ISO image into the storage device, makes the device bootable and creates the data partition where the user data is kept across reboots. Once that the ISO has been deployed the user can restart and boot into the storage device to select the system.
How is it different than using an installer? znx follows the concept of AppImages which is that software isn’t “installed,” but it is instead deployed. That means that you don’t get lots of files and folders distributed in a filesystem but just one file, same with znx, instead of unpacking the squashfs file (the compressed filesystem that holds the actual OS) and extracting the contents to the target device (thus “installing” the OS the traditional way). The OS remains as one file which can be updated using a zsync file for differential updates (so-called delta updates which is what znx does, similarly, AppImageUpdate performs updates to AppImages only updating the bits that changed) or replacing the entire file, i.e., downloading a new ISO that replaces the old one.
Where is my data stored then? Any file that the user creates is kept in the data partition. To install new software (by the software we mean desktop applications like Firefox, LibreOffice, etc.) the go-to method would be to get an AppImage. These AppImages are kept when the user updates the deployed ISO to a new version.
Alright, but what would be the benefits of using znx? An immediate benefit is that multiple systems can be deployed at once which allows the user to perform rollbacks and switch between them. When a new version of the distribution is available, the user would only have to download the differential zsync file instead of having to reinstall the system, think like OTA updates on mobiles. Or instead of having to rely on pre-compiled binary packages (like Debian packages, RPM packages, etc.) that can lead to unmet dependencies, broken packages, and related inconveniences during full-system upgrades the user would download the new version entirely or use the differential zsync file.
It also would provide a way to have a factory reset method available at any moment, i.e., immutable filesystems. Or for businesses znx would be able to offer an OEM-mode that would facilitate the deployment of the operating system.
Sponsor us. Help Nitrux achieve more, together.
We build Nitrux because we love it and there is no pressure to sponsor, however, we do welcome anything that you can spare. By sponsoring Nitrux you contribute by giving the development team a regular and predictable income to cover our hosting, development, and hardware testing costs. Donated funds are used to finance the needs of the project including, but not limited to, hosting/server costs, equipment, and funding the work of the people behind it. You can donate any amount you want. The team behind Nitrux will appreciate all donations as they will help bring this wonderful project to the same level of quality as that of the much larger, top-tier projects.
- Facebook https://www.facebook.com/Nitrux
- Twitter https://twitter.com/Nitrux_NX
- Mastodon https://mastodon.cloud/@Nitrux_NX
- Instagram https://instagram.com/nitrux_nx
- MeWe https://mewe.com/p/nitrux
- YouTube https://www.youtube.com/c/NitruxInside
- Gitter https://gitter.im/Nitrux/public
- GitHub https://github.com/Nitrux
Nitrux_NX owns the following accounts on other platforms:
Nitrux_NX joined 7 months ago.