The Solus Project team recently announced the immediate availability of Solus Operating System Beta 2. This release is available for 64-bit systems, and is now available for EFI machines. This release is the first new ISO since the project rebrand, and marks many technological changes.
According to Solus Project team, they have switched to HTTPS-only software repositories and implemented delta updates with highly compressed packages for quick, safe and bandwidth-friendly software management. Driver management is now available for NVIDIA users, and AMD driver management will feature in the coming weeks.
- Linux 4.0.3
- GNOME Stack 3.16.3
- Budgie Desktop 8.2
- Firefox 38.0.1
- UEFI support (boot and installation)
- NVIDIA proprietary driver support (346.xxx) – users simply install ‘nvidia-glx-driver’ from System/X.Org Drivers in Software Center
- Switched to Solus-specific artwork, EvoPop.
- X.Org 1.17.1 + Mesa 10.5.3
- Completed rebrand.
- All new packages developed for the Solus Operating System now use the ypkg format. Nearly 20% of our repository is now using the format.
- Switch to HTTPS-only software sources
- Buildbot based build system using efficient hardlink-centric repository management, with automatic deltas.
- Repo-wide ABI freeze in place prior to RC1 path.
- Long-standing Budgie performance and usability bugs addressed relating to X11 grab/focus cycles. Keybindings now work correctly across the board. Reduced memory footprint.
- VirtualBox and Qemu now using the modesetting driver
- 551 package repository commits: 1326 files changed, 53700 insertions(+), 34616 deletions
Note on Virtualization
Note that whilst virtualisation solutions such as VirtualBox or Qemu can indeed be useful for preliminary testing of Solus, they will suffer greatly degraded performance in comparison to a hardware install. This is because Solus is optimised for real hardware usage, and doesn’t cut corners or accomdate for virtual scenarios. As such the desktop itself requires 3D acceleration, which is commonplace for a long time. Whilst running Solus in a virtual environment it will rely on software (CPU) rendering, as such you will see high CPU usage and degraded performance. This is in no way an indicator of performance on real hardware.comments powered by Disqus