 DistroWatch Weekly |
| DistroWatch Weekly, Issue 872, 29 June 2020 |
Welcome to this year's 26th issue of DistroWatch Weekly!
When entering into the world of free and open source software it can be difficult to understand how open source licenses work. When one is accustomed to dealing with closed source software, controlled by one company, being introduced to an environment where anyone can modify and redistribute an operating system's components can seem quite foreign. This week we explore the topic of who controls access to the Linux kernel and its code in our Questions and Answers column. We also try to clear up some questions about open source library licensing with regards to popular desktop toolkits like Qt and GTK. First though we talk about GoboLinux, an unusual distribution that tries to reorganize the Linux filesystem and do away with the need for a traditional package manager. What do you think of GoboLinux's modular approach to filesystem organization? Let us know in this week's Opinion Poll. Then, in our News section, we discuss WireGuard support coming to OpenBSD and UBports starting to run on more mobile devices. We also talk about KISS getting new features and Fedora selecting a new default text editor and filesystem. We are also pleased to share the releases of the past week and list the torrents we're seeding. We wish you all a superb week and happy reading!
Content:
- Review: GoboLinux 017
- News: OpenBSD adopts WireGuard, UBports coming to more devices, Fedora plans to set a default text editor, KISS getting new package manager
- Questions and answers: Controlling access to the kernel and understanding software development licenses
- Released last week: Linux Mint 20, Grml 2020.06
- Torrent corner: Bluestar, EasyOS, Grml, KDE neon, Linux Mint, Live Raizo, Nitrux, Q4OS, Redo Rescue, Rescuezilla, Robolinux
- Upcoming releases: Tails 4.8, openSUSE 15.2
- Opinion poll: The filesystem layout
- Reader comments
Listen to the Podcast edition of this week's DistroWatch Weekly in OGG (19MB) and MP3 (14MB) formats.
|
| Feature Story (by Jesse Smith) |
GoboLinux 017
The GoboLinux project develops a distribution with an unusual goal: reorganizing the operating system's filesystem. The project introduces itself as follows:
GoboLinux is an alternative Linux distribution which redefines the entire filesystem hierarchy. In GoboLinux you don't need a package database because the filesystem is the database: each program resides in its own directory.
In other words, instead of a package manager placing executable files in /usr/bin, libraries in /usr/lib, and other resources in /usr/share, a program's files are all stored in one tree, such as /Programs/Firefox or /Programs/LibreOffice. This way the user, and package utilities, can remove software by deleting a single directory rather than keeping track of where individual files have been installed.
GoboLinux uses the the Awesome window manager, which provides a lightweight graphical interface. Version 017 of Gobo removes Python2 in favour of Python3, and also removes GTK2 for GTK3 on the ISO. Audio management is now handled by PulseAudio.
Gobo makes available one edition of the distribution for 64-bit (x86_64) computers. The download is 1.9GB in size. Booting from this media brings up a series of text-based menus. These menus ask us to select one of six languages from a list, then select our keyboard's layout. With these questions answered we are presented with a text console where we are automatically logged into the root account. A message appears above the command line prompt which lets us know we can run "startx" to open a graphical user interface. The text also explains how to launch the system installer from either the command line or from the Awesome window manager.
Opening the Awesome environment places a panel at the top of the screen. We can find an application menu in the upper-left corner and the system tray in the upper-right. The wallpaper is mostly black with abstract designs drawn on it. The background appears to be dynamically drawn rather than a fixed image. The volume icon is interesting in that clicking on it changes the colour of the icon (toggling between green and red) and this appears to mute audio.
The application menu in the live environment contains very few entries. Most of these manage or adjust the Awesome session. I feel it worth noting that to customize Awesome we need to edit a text file, there isn't any point-and-click settings panel. There is a menu entry to open the Awesome manual. Trying to access the manual caused a window to open for a second, then immediately crash without showing the requested documentation or an error.
GoboLinux 017 -- The Awesome window manager
(full image size: 162kB, resolution: 1366x768 pixels)
There are also some utilities such as the GParted partition manager and a terminal. I will talk about the included software more later, but almost everything included in the menu is intended to either manage Awesome or get the system ready to install Gobo on the hard drive.
Installing
The Gobo installer, when launched from Awesome, is a graphical desktop application. The installer does not have a method for managing partitions and if the installer cannot find a suitable partition for the operating system, the installer will ask us to launch a tool such as GParted or cfdisk to set up a new partition for it.
Assuming the installer finds a suitable partition it will ask which partition it should use for the root filesystem and if the partition should be formatted. Gobo appears only support the ext4 filesystem. We are given the option of creating a swap file. I skipped this step as I have a dedicated swap partition, but the installer does not provide an option for using the existing swap space. This meant I started my trial without swap space, but had the option of manually adding it later. The installer also does not appear to support keeping users' home directories on a separate partition.
The installer next lists all the packages that will be installed. We can uncheck boxes to exclude items we do not want. The list is quite long and it probably is not practical to go through it item-by-item. Most packages have a brief description next to them to help us figure out what we want, but a few do not. I opted to simply install all the packages which is the default behaviour.
The installer next walks us through installing the boot loader (and choosing where it should be placed), confirming our keyboard layout, the boot theme, and our clock's settings. Then we make up a root password and create one (or more) additional user accounts. I like being able to make multiple user accounts up front. The installer then showed me detailed progress reports as it copied files to my hard drive and reported it had successfully finished a short time later.
Early impressions
Gobo boots to a text console where we can sign into our account. The default approach with Gobo is to use the command line. While this will not be appealing to many people, it is light on resources. Users can access a graphical desktop by typing "startx" from the command line.
The console environment uses the zsh shell by default and includes the usual UNIX-style command line utilities. The man program is included but there are no manual pages, making it hard to get local help with the command line.
Included software
Once we launch the Awesome window manager we have access to a small collection of desktop software. Programs such as the Firefox browser, Audacity media player, and vim editor are on hand. Some system tools like GParted and the Htop process monitor are included too. While zsh is the default shell, others are available. The bash shell is included by default and other shells are in the project's software repository. The sudo utility is provided to help users perform administrative tasks. In the background we find Gobo uses the SysV init software and version 5.6.10 of the Linux kernel.
GoboLinux 017 -- Running the Firefox web browser
(full image size: 634kB, resolution: 1366x768 pixels)
Hardware
When Gobo is running just a text console it is pleasantly light on resources. The CPU pretty much sits idle and the system consumes 50MB of RAM. Even when logged into Awesome, the distribution uses a mere 150MB of memory and very little of the CPU. A full install takes about 6GB of disk space, which seems like a lot considering how few desktop tools are included. However, I believe much of the space is consumed by build tools as Gobo builds new software from source code. (More on installing software in a minute.)
I started running Gobo in a VirtualBox environment and, for the most part, the distribution ran well. It was a little slow to boot, but after that ran quickly. Sound, networking, and the desktop environment all worked. My one serious issue was I could not get the Awesome interface to resize. It was stuck at a low resolution and would not resize dynamically with the virtual machine's window. Awesome also does not appear to have a built-in tool to adjust the screen resolution which hampered my use of Gobo in the virtual environment.
Things went better when I switched over to running Gobo on my laptop. Audio and wireless networking functioned smoothly. The desktop used my full screen resolution. The distribution was still a little slow to boot, but ran well after that - with one exception which I am about to share.
Software management
The distribution uses a tool called Compile to download source code, build it and install it into a directory tree. Compile uses supplied build instructions, called recipes to figure out how to download and build software. According to the documentation, we can typically use "sudo Compile <package name>" to install new software. Building new packages from source code makes the process very slow as each package and its dependencies needs to be built from scratch. Unfortunately there does not appear to be a search feature built into Compile and I had to browse recipes on-line to find out what software was available.
Compile appears to clone an on-line repository of recipes like a ports tree on other distros. It took a long time just trying to get a copy of the repository. There was no sign of progress, even when Compile was run in verbose mode.
After trying six times and never getting a copy of the repository, despite having an active (and fast) Internet connection, I found Compile would always hang on cloning the Git repository. No data was being downloaded after the initial Git files were created. Even after several minutes, no new data was added to my repository tree. This doesn't doesn't appear to be an issue with Compile specifically as using the git command line tool would also hang trying to get the Recipes repository, and always stopped after downloading 112kB of the 474MB repository.
I tried downloading the git repository from another computer on the same network and the Recipes repository downloaded without any problems in a minute, so the issue was not the GitHub server or the local network.
Next I tried manually copying the recipes from my other computer to the Gobo system. With the recipes repository manually installed Compile no longer tried to download it. However, Compile would still hang when instructed to install software and it still showed no messages when run in verbose mode. In addition, there was no activity on the disk or network. The process monitor showed no activity from Compile. I tried installing multiple packages, all with the same result - nothing would happen and no error message was given.
On a related issue, when exploring large directories or sub-directories, my shell used a lot of disk activity just doing simple things like using cd or running pwd. This only happened in directories with many entries like /Programs or /Data/Compile/Recipes. When exploring directories with few entries the shell was immediately responsive and used almost no resources. I found this issue only happened when running the default zsh shell. Switching to bash removed the lock-up in large directories.
I had hoped running Compile again from bash would provide a solution to my package management problem, but it did not. Trying to run Compile, or git, on data that included a lot of files, caused the shell to hang.
Filesystem organization
Gobo's claim to fame isn't software management exactly, it is filesystem organization. Traditional Linux filesystems contain directories such as etc, usr, and home. Gobo names directories differently and the root filesystem contains directories called Data, Mount, Programs, System, and Users. This is nice in that it is more obvious what directories contain which resources.
Technically, the directories usr, etc, and so on still exist on a Gobo system. These legacy entries are simply hidden from the user. We can still cd into them, but do not see them in directory listings. Typically, the contents of these locations are symbolic links to Gobo's custom locations, though not always. For example, the /etc/passwd file, containing user account information still exists. However, the /etc/zshrc file is a symbolic link to /Programs/Scripts/Settings/zshrc. This hiding of traditional locations means the filesystem looks cleaner and is organized in a way which makes the contents of directories clearer to newcomers.
The irony here, to my mind, is only advanced Linux users are likely to ever use Gobo because it requires a more technical knowledge and experience to run. However, the people who will benefit from the reorganization of directories into clearly named modules are almost exclusively Linux newcomers.
Conclusions
Renaming directories is not the only strength Gobo offers. Modularly stored programs can be useful. It means we can easily see what programs are installed, which versions are available, and deleting programs is as easy as deleting their directory. In theory this makes the filesystem itself our package database. This is, to my mind, a neat idea.
However, I see a few issues with this approach. One, on the practical side, is I could not get the Compile tool to actually download and install any software. However, let's assume this is a rare quirk on my end and usually Compile works perfectly. Then we still have three main issues, as I see things.
First, Compile builds packages from source code and this is very slow. Most users do not want to wait around for a few hours while their web browser updates just so their underlying filesystem can be organized more modularly. I'm not saying the modular approach isn't appealing, just that the cost (compiling everything from scratch) is expensive. If Gobo had pre-built packages this would no longer be an issue.
Second, most modern package managers (such as DNF, APT, and pacman) do a good enough job that users are probably just as well off with them as with a modular filesystem that acts as a package database. These tools make running searches, removing old packages, and checking dependencies relatively painless and accomplish about the same result as Gobo's layout. There is an argument to be made that package managers add complexity to the system and removing them in favour of a new filesystem layout is better (more in line with the KISS philosophy). And I would agree with that idea, in theory, but I'm not sure Gobo's approach is practically better because....
Third, modern Linux distribution deal with tens of thousands of software packages. Gobo's modular approach (the filesystem is the package database) makes sense in small scale environments. But I'm not so sure it works practically on a system with 50,000 packages. There is no way I'm going to hunt down individual packages manually, modularly organized or not, on a modern distribution. The directory is too large. At best, I will use a command line string like "find /Programs -type d | grep -i falkon" to see if the Falkon browser is installed. At the end of the day, is that any better or worse than "dpkg -l | grep -i falkon" on a Debian-based system? Is "find /Data/Compile/Recipes -type d | grep -i supertux" really better than running "apt search supertux" from the user's perspective? I can see technical arguments for both sides, but ultimately, as a user, I want the tool that makes my life easier and my system faster to use.
All in all, I think what Gobo is doing is interesting. If nothing else it is an appealing experiment that provides an alternative approach and something to think about. Plus it makes the filesystem look cleaner and less arcane for newcomers. In my case, I found it was not a practical tool (at least when it came to package management), but I do like that the Gobo developers are thinking outside the box and offering a way to overhaul package management and the filesystem hierarchy.
* * * * *
Hardware used in this review
My physical test equipment for this review was a de-branded HP laptop with the following
specifications:
- Processor: Intel i3 2.5GHz CPU
- Display: Intel integrated video
- Storage: Western Digital 700GB hard drive
- Memory: 6GB of RAM
- Wired network device: Realtek RTL8101E/RTL8102E PCI Express Fast
- Wireless network device: Realtek RTL8188EE Wireless network card
* * * * *
Visitor supplied rating
GoboLinux has a visitor supplied average rating of: 4.3/10 from 3 review(s).
Have you used GoboLinux? You can leave your own review of the project on our ratings page.
|
| Miscellaneous News (by Jesse Smith) |
OpenBSD adopts WireGuard, UBports coming to more devices, Fedora plans to set a default text editor, KISS gets new package manager
Jason Donenfeld has announced that he and Matt Dunwoodie have added WireGuard, a small, fast VPN service, to the OpenBSD kernel. The new WireGuard implementation is expected to be available in OpenBSD 6.8. "I'm happy to announce that WireGuard has been merged into the OpenBSD kernel, with integration into userland as well. Matt Dunwoodie and I have been working on this for quite some time now, with at some point Matt even showing up at my door in Paris to push the effort further. This marks the culmination of quite a bit of effort, and certainly a multi-year project for Matt. I should also note that the upstreaming process to OpenBSD was extremely pleasant. We did three patch revisions, with useful feedback on each one and a very supportive community. I imagine that this work will ship with OpenBSD 6.8."
* * * * *
People wishing to run a GNU/Linux operating system on their mobile devices are a little closer to that goal as UBports is making progress on multiple fronts. The project's latest newsletter mentions some work being done on specific ports: "Alfred reported progress with porting. A lot of new devices keep appearing. Builds are now on the server for many although with graphical support in the form of the installer not as yet. Galaxy Note 4, Xperia Performance and others are now up. Instead of individual branches under the names of those porting devices, everything now appears in a single channel. It is also immediately clear which version and architecture are involved, so it is much easier to understand and use. Erfan has done a lot more. Android 9 device names show up correctly on the push server. Kernel patches have been implemented to remedy the missing battery charge indicator on some devices. Brightness, time settings and other indicators have all seen fixes. Notkit has developed a working port for the F(x)tech device with the sliding keyboard! Marius has UT 'running' on his PineBook Pro although it is not usable at all at the moment. There is for example no mouse at all..."
There has also been progress in running UBports on a generic system image (GSI) which would open up possibilities for running UBports on many Android devices. A post on xda-developers discusses how a generic base can allow UBports to run on multiple devices.
* * * * *
The Fedora distribution does not currently set a default text editor, leaving which editor to use up to either the user or whichever program is being run. This can result in some awkward moments when a tool, such as git, needs to pick a default editor for us when none is provided. Ben Cotton explains: "Fedora does not currently have a default terminal text editor, because
the $EDITOR environment variable is unset by default. But a common scenario where users wind up in a terminal text editor is when using 'git commit'. By default, git picks vi. You need to spend time learning how to use it, for even basic editing tasks. This increases the barrier to entry for those who are switching to Fedora and don't know how to use vi." The proposal suggests making Nano the default terminal editor as it is relatively straight forward to use and offers on-screen prompts.
Another proposal indicates Fedora 33 may ship with Btrfs as the default filesystem. This would allow users to make snapshots of their system prior to upgrades and expand storage across multiple disks with minimal effort.
* * * * *
The KISS project is in the process of making some significant changes. The project is experimenting with a new package manager (written in C, rather than shell script), and two new desktop environments have been ported to KISS: "Dilyn Corner has successfully ported KDE to KISS! I mentioned this last month though it only recently reached a usable state. This is wonderful to see! LXQt comes to KISS: This is still in its early stages though Eudald Gubert Roldan has begun the work in porting LXQt to KISS." The KISS project is also being ported to ARMv7 which should allow the operating system to run on a range of low-power ARM devices.
* * * * *
These and other news stories can be found on our Headlines page.
|
| Questions and Answers (by Jesse Smith) |
Controlling access to the kernel and understanding software development licenses
Protecting-the-kernel asks: I know that most Linux kernel development is done by large, for-profit companies. Who gets to decide whether a patch gets approved in the mainline kernel? It seems critical to me to prevent big corporations from driving the kernel towards their own interests. Linus Torvalds can't be approving every single patch that lands in the kernel so who controls access?
DistroWatch answers: There are a few answers to this question. The Linux kernel is huge, featuring millions of lines of code. No one person really audits the whole thing. Instead, components of the kernel are usually maintained by certain key, long-term developers. Generally a patch will get submitted by a developer (or company) to whomever is considered the maintainer for that section of the kernel. The maintainer will look it over, suggest changes and, if everything seems to be in order, will accept the change into their copy of the kernel's source code. Changes then tend to make their way up through the hierarchy.
The official Linux kernel, the one that gets published at kernel.org, is Linus Torvalds' version of the kernel source code. That doesn't mean he goes through every line or change personally, but he does have final say over what he publishes as the official kernel. If something doesn't look right or there is a dispute between developers, Torvalds gets to decide what goes into his official Linux source code and what does not.
However, that is only part of the answer. Since Linux is open source, Torvalds' kernel is just one version of the Linux source code. What Torvalds chooses to put in his kernel only matters if you download and install your own kernel from the official Linux repository at kernel.org. If you are running a kernel provided by your distribution, then the package maintainer is the one who decides what patches or modules get included and what gets stripped out.
This means that the official kernel.org version of Linux, the version that ships with Red Hat Enterprise Linux, the version in Ubuntu, the Android kernel, and the deblobbed kernel in Trisquel GNU/Linux are all slightly different. They may all be variations of Torvalds' kernel, but they will have different feature patches, enabled drivers, and security fixes applied. These changes are decided by whomever builds the kernel package for your distribution.
In short, while Linus Torvalds ultimately decides what is officially Linux, due to the project's open source nature the person who has final say over what is in your copy of the Linux kernel is whomever compiled it for you.
* * * * *
Building-software-with-a-toolkit asks: In case one wants to develop closed sourced software, then I think a developer must buy a Qt license and they can then distribute (Qt and their application) as closed source. Please confirm.
How does this work for GTK/GNOME? How can closed source software be developed and sold using the GTK toolkit for GNOME/Xfce or KDE?
DistroWatch answers: The Qt development toolkit is (mostly) open source and is available under an open source license. Specifically Qt is available under the GNU Lesser General Public License (LGPL) version 3. This is a big part of why Qt software is popular in the Linux and BSD communities. Particularly with the KDE, Lumina, and LXQt projects.
The Qt software is also available under a commercial license which allows developers to build and distribute closed source software. You can learn more about how Qt handles this dual licensing on the Qt licensing page.
The GTK library is also open source and licensed in a very similar way. According to the GTK website the library is available under the GNU Library General Public License version 2. While GTK is typically used to create open source applications, it is not a requirement of the license and a developer does not need to do anything special to create and distribute closed source programs with GTK. The license sums up the situation fairly simply:
A program that contains no derivative of any portion of the Library, but is designed to work with the Library by being compiled or linked with it, is called a "work that uses the Library". Such a work, in isolation, is not a derivative work of the Library, and therefore falls outside the scope of this License.
While it is technically and legally possible to create closed source applications using either Qt or GTK, most developers see the benefit of sharing their source code and encouraging people to tweak and improve their software. This keeps the software ecosystem healthier and helps fix bugs faster. This is why it is relatively rare to see closed source GTK or Qt applications in the wild.
* * * * *
Additional answers can be found in our Questions and Answers archive.
|
| Released Last Week |
Grml 2020.06
Michael Prokop has announced the release of Grml 2020.06, a new version of the project's Linux distribution designed for system administrators, based on Debian's "testing" branch: "Grml - new stable release 2020.06 available. This Grml release provides fresh software packages from Debian testing ('bullseye'). As usual it also incorporates current hardware support and fixes known bugs from the previous Grml release. Important changes: the default mount point for the live system was changed; tools like grml2usb, grml-paste and grml-x have been ported from Python 2 to Python 3 - we no longer support Python 2 in our tools; the live system no longer uses a custom Grml kernel - instead we switched to the 'linux-image' packages provided by Debian. New features: cloud-init support - a standard multi-distribution method for cross-platform cloud instance initialization; qemu-guest-agent support - this daemon exchanges information between the host and guest system; network information in grml-quickconfig - hostname, cloud-init, IP addresses and zeroconf/avahi information...." See the release announcement and release notes for a detailed description of this new release.
Linux Mint 20
The Linux Mint team have announced the release of Linux Mint 20. The new version is based on Ubuntu 20.04 and provides five years of support. The new release is available in three flavours: Cinnamon, MATE, and Xfce. Linux Mint 20 offers support for different scaling on HiDPI displays, includes a new tool called Warpinator for sharing files on the local area network, and the welcome window provides quick access to changing the desktop colour theme. "The star of the show in Linux Mint 20 is a new application called Warpinator. 10 years ago, Linux Mint 6 featured a tool called "Giver" which could share files across the local network. Without any server or configuration, computers would automatically see each others and you could simply drag and drop files from one to another. When the Giver project was discontinued it had to be removed from Linux Mint and we've been missing that functionality ever since. Warpinator is a reimplementation of Giver. Server configuration (FTP, NFS, Samba) is overkill for casual file transfers between two computers, and it's a real pity to use external media (Internet services, USB sticks, external HDDs) just to share files when there's a local network which could do just that." Further information can be found in the project's release announcements (Cinnamon, MATE, Xfce) and in the release notes (Cinnamon, MATE, Xfce).
Linux Mint 20 -- Running the Cinnamon desktop
(full image size: 861kB, resolution: 1920x1080 pixels)
* * * * *
Development, unannounced and minor bug-fix releases
|
| Torrent Corner |
Weekly Torrents
The table below provides a list of torrents DistroWatch is currently seeding. If you do not have a bittorrent client capable of handling the linked files, we suggest installing either the Transmission or KTorrent bittorrent clients.
Archives of our previously seeded torrents may be found in our Torrent Archive. We also maintain a Torrents RSS feed for people who wish to have open source torrents delivered to them. To share your own open source torrents of Linux and BSD projects, please visit our Upload Torrents page.
Torrent Corner statistics:
- Total torrents seeded: 2,042
- Total data uploaded: 32.4TB
|
| Upcoming Releases and Announcements |
|
Summary of expected upcoming releases
|
| Opinion Poll (by Jesse Smith) |
The filesystem layout
In this week's review of GoboLinux we mentioned an alternative filesystem layout. Typically GNU/Linux distributions arrange their filesystems in a way which places executable files all together in one place, libraries together in another, and other resources in a third location. This keeps types of resources together. GoboLinux takes another approach, packaging all the files associated with a specific package in one directory tree. This results in more directories (one for each package), while keeping the resources of each program separate from the resources of other packages.
We would like to hear which approach you think is better. Do you like the idea of each program having its own modular directory, or all similar resources (programs and libraries) being stored in one big directory together?
You can see the results of our previous poll on distributions supporting multiple init systems in last week's edition. All previous poll results can be found in our poll archives.
|
The filesystem layout
| I prefer all similar resources in one directory: | 429 (36%) |
| I prefer modular directories for each program: | 363 (30%) |
| I prefer another approach: | 43 (4%) |
| I have no preference: | 372 (31%) |
|
|
| Website News (by Jesse Smith) |
Distributions added to waiting list
- Emperor-OS. Emperor-OS is an Ubuntu-based distribution which includes hundreds of packages that can be used for programming and data science tasks.
* * * * *
DistroWatch database summary
* * * * *
This concludes this week's issue of DistroWatch Weekly. The next instalment will be published on Monday, 6 July 2020. Past articles and reviews can be found through our Article Search page. To contact the authors please send e-mail to:
- Jesse Smith (feedback, questions and suggestions: distribution reviews/submissions, questions and answers, tips and tricks)
- Ladislav Bodnar (feedback, questions, donations, comments)
- Bruce Patterson (podcast)
|
|
| Tip Jar |
If you've enjoyed this week's issue of DistroWatch Weekly, please consider sending us a tip.
(Tips this week: 1, value: US$3.69) |
|
|
|
 bc1qxes3k2wq3uqzr074tkwwjmwfe63z70gwzfu4lx  lnurl1dp68gurn8ghj7ampd3kx2ar0veekzar0wd5xjtnrdakj7tnhv4kxctttdehhwm30d3h82unvwqhhxarpw3jkc7tzw4ex6cfexyfua2nr  86fA3qPTeQtNb2k1vLwEQaAp3XxkvvvXt69gSG5LGunXXikK9koPWZaRQgfFPBPWhMgXjPjccy9LA9xRFchPWQAnPvxh5Le paypal.me/distrowatchweekly • patreon.com/distrowatch |
|
| Extended Lifecycle Support by TuxCare |
|
|
|
| TUXEDO |
TUXEDO Computers - Linux Hardware in a tailor made suite
Choose from a wide range of laptops and PCs in various sizes and shapes at TUXEDOComputers.com. Every machine comes pre-installed and ready-to-run with Linux. Full 24 months of warranty and lifetime support included!
Learn more about our full service package and all benefits from buying at TUXEDO.
|
| Archives |
| • Issue 1091 (2024-10-07): Redox OS 0.9.0, Unified package management vs universal package formats, Redox begins RISC-V port, Mint polishes interface, Qubes certifies new laptop |
| • Issue 1090 (2024-09-30): Rhino Linux 2024.2, commercial distros with alternative desktops, Valve seeks to improve Wayland performance, HardenedBSD parterns with Protectli, Tails merges with Tor Project, Quantum Leap partners with the FreeBSD Foundation |
| • Issue 1089 (2024-09-23): Expirion 6.0, openKylin 2.0, managing configuration files, the future of Linux development, fixing bugs in Haiku, Slackware packages dracut |
| • Issue 1088 (2024-09-16): PorteuX 1.6, migrating from Windows 10 to which Linux distro, making NetBSD immutable, AlmaLinux offers hardware certification, Mint updates old APT tools |
| • Issue 1087 (2024-09-09): COSMIC desktop, running cron jobs at variable times, UBports highlights new apps, HardenedBSD offers work around for FreeBSD change, Debian considers how to cull old packages, systemd ported to musl |
| • Issue 1086 (2024-09-02): Vanilla OS 2, command line tips for simple tasks, FreeBSD receives investment from STF, openSUSE Tumbleweed update can break network connections, Debian refreshes media |
| • Issue 1085 (2024-08-26): Nobara 40, OpenMandriva 24.07 "ROME", distros which include source code, FreeBSD publishes quarterly report, Microsoft updates breaks Linux in dual-boot environments |
| • Issue 1084 (2024-08-19): Liya 2.0, dual boot with encryption, Haiku introduces performance improvements, Gentoo dropping IA-64, Redcore merges major upgrade |
| • Issue 1083 (2024-08-12): TrueNAS 24.04.2 "SCALE", Linux distros for smartphones, Redox OS introduces web server, PipeWire exposes battery drain on Linux, Canonical updates kernel version policy |
| • Issue 1082 (2024-08-05): Linux Mint 22, taking snapshots of UFS on FreeBSD, openSUSE updates Tumbleweed and Aeon, Debian creates Tiny QA Tasks, Manjaro testing immutable images |
| • Issue 1081 (2024-07-29): SysLinuxOS 12.4, OpenBSD gain hardware acceleration, Slackware changes kernel naming, Mint publishes upgrade instructions |
| • Issue 1080 (2024-07-22): Running GNU/Linux on Android with Andronix, protecting network services, Solus dropping AppArmor and Snap, openSUSE Aeon Desktop gaining full disk encryption, SUSE asks openSUSE to change its branding |
| • Issue 1079 (2024-07-15): Ubuntu Core 24, hiding files on Linux, Fedora dropping X11 packages on Workstation, Red Hat phasing out GRUB, new OpenSSH vulnerability, FreeBSD speeds up release cycle, UBports testing new first-run wizard |
| • Issue 1078 (2024-07-08): Changing init software, server machines running desktop environments, OpenSSH vulnerability patched, Peppermint launches new edition, HardenedBSD updates ports |
| • Issue 1077 (2024-07-01): The Unity and Lomiri interfaces, different distros for different tasks, Ubuntu plans to run Wayland on NVIDIA cards, openSUSE updates Leap Micro, Debian releases refreshed media, UBports gaining contact synchronisation, FreeDOS celebrates its 30th anniversary |
| • Issue 1076 (2024-06-24): openSUSE 15.6, what makes Linux unique, SUSE Liberty Linux to support CentOS Linux 7, SLE receives 19 years of support, openSUSE testing Leap Micro edition |
| • Issue 1075 (2024-06-17): Redox OS, X11 and Wayland on the BSDs, AlmaLinux releases Pi build, Canonical announces RISC-V laptop with Ubuntu, key changes in systemd |
| • Issue 1074 (2024-06-10): Endless OS 6.0.0, distros with init diversity, Mint to filter unverified Flatpaks, Debian adds systemd-boot options, Redox adopts COSMIC desktop, OpenSSH gains new security features |
| • Issue 1073 (2024-06-03): LXQt 2.0.0, an overview of Linux desktop environments, Canonical partners with Milk-V, openSUSE introduces new features in Aeon Desktop, Fedora mirrors see rise in traffic, Wayland adds OpenBSD support |
| • Issue 1072 (2024-05-27): Manjaro 24.0, comparing init software, OpenBSD ports Plasma 6, Arch community debates mirror requirements, ThinOS to upgrade its FreeBSD core |
| • Issue 1071 (2024-05-20): Archcraft 2024.04.06, common command line mistakes, ReactOS imports WINE improvements, Haiku makes adjusting themes easier, NetBSD takes a stand against code generated by chatbots |
| • Issue 1070 (2024-05-13): Damn Small Linux 2024, hiding kernel messages during boot, Red Hat offers AI edition, new web browser for UBports, Fedora Asahi Remix 40 released, Qubes extends support for version 4.1 |
| • Issue 1069 (2024-05-06): Ubuntu 24.04, installing packages in alternative locations, systemd creates sudo alternative, Mint encourages XApps collaboration, FreeBSD publishes quarterly update |
| • Issue 1068 (2024-04-29): Fedora 40, transforming one distro into another, Debian elects new Project Leader, Red Hat extends support cycle, Emmabuntus adds accessibility features, Canonical's new security features |
| • Issue 1067 (2024-04-22): LocalSend for transferring files, detecting supported CPU architecure levels, new visual design for APT, Fedora and openSUSE working on reproducible builds, LXQt released, AlmaLinux re-adds hardware support |
| • Issue 1066 (2024-04-15): Fun projects to do with the Raspberry Pi and PinePhone, installing new software on fixed-release distributions, improving GNOME Terminal performance, Mint testing new repository mirrors, Gentoo becomes a Software In the Public Interest project |
| • Issue 1065 (2024-04-08): Dr.Parted Live 24.03, answering questions about the xz exploit, Linux Mint to ship HWE kernel, AlmaLinux patches flaw ahead of upstream Red Hat, Calculate changes release model |
| • Issue 1064 (2024-04-01): NixOS 23.11, the status of Hurd, liblzma compromised upstream, FreeBSD Foundation focuses on improving wireless networking, Ubuntu Pro offers 12 years of support |
| • Issue 1063 (2024-03-25): Redcore Linux 2401, how slowly can a rolling release update, Debian starts new Project Leader election, Red Hat creating new NVIDIA driver, Snap store hit with more malware |
| • Issue 1062 (2024-03-18): KDE neon 20240304, changing file permissions, Canonical turns 20, Pop!_OS creates new software centre, openSUSE packages Plasma 6 |
| • Issue 1061 (2024-03-11): Using a PinePhone as a workstation, restarting background services on a schedule, NixBSD ports Nix to FreeBSD, Fedora packaging COSMIC, postmarketOS to adopt systemd, Linux Mint replacing HexChat |
| • Issue 1060 (2024-03-04): AV Linux MX-23.1, bootstrapping a network connection, key OpenBSD features, Qubes certifies new hardware, LXQt and Plasma migrate to Qt 6 |
| • Issue 1059 (2024-02-26): Warp Terminal, navigating manual pages, malware found in the Snap store, Red Hat considering CPU requirement update, UBports organizes ongoing work |
| • Issue 1058 (2024-02-19): Drauger OS 7.6, how much disk space to allocate, System76 prepares to launch COSMIC desktop, UBports changes its version scheme, TrueNAS to offer faster deduplication |
| • Issue 1057 (2024-02-12): Adelie Linux 1.0 Beta, rolling release vs fixed for a smoother experience, Debian working on 2038 bug, elementary OS to split applications from base system updates, Fedora announces Atomic Desktops |
| • Issue 1056 (2024-02-05): wattOS R13, the various write speeds of ISO writing tools, DSL returns, Mint faces Wayland challenges, HardenedBSD blocks foreign USB devices, Gentoo publishes new repository, Linux distros patch glibc flaw |
| • Issue 1055 (2024-01-29): CNIX OS 231204, distributions patching packages the most, Gentoo team presents ongoing work, UBports introduces connectivity and battery improvements, interview with Haiku developer |
| • Issue 1054 (2024-01-22): Solus 4.5, comparing dd and cp when writing ISO files, openSUSE plans new major Leap version, XeroLinux shutting down, HardenedBSD changes its build schedule |
| • Issue 1053 (2024-01-15): Linux AI voice assistants, some distributions running hotter than others, UBports talks about coming changes, Qubes certifies StarBook laptops, Asahi Linux improves energy savings |
| • Issue 1052 (2024-01-08): OpenMandriva Lx 5.0, keeping shell commands running when theterminal closes, Mint upgrades Edge kernel, Vanilla OS plans big changes, Canonical working to make Snap more cross-platform |
| • Issue 1051 (2024-01-01): Favourite distros of 2023, reloading shell settings, Asahi Linux releases Fedora remix, Gentoo offers binary packages, openSUSE provides full disk encryption |
| • Issue 1050 (2023-12-18): rlxos 2023.11, renaming files and opening terminal windows in specific directories, TrueNAS publishes ZFS fixes, Debian publishes delayed install media, Haiku polishes desktop experience |
| • Issue 1049 (2023-12-11): Lernstick 12, alternatives to WINE, openSUSE updates its branding, Mint unveils new features, Lubuntu team plans for 24.04 |
| • Issue 1048 (2023-12-04): openSUSE MicroOS, the transition from X11 to Wayland, Red Hat phasing out X11 packages, UBports making mobile development easier |
| • Issue 1047 (2023-11-27): GhostBSD 23.10.1, Why Linux uses swap when memory is free, Ubuntu Budgie may benefit from Wayland work in Xfce, early issues with FreeBSD 14.0 |
| • Issue 1046 (2023-11-20): Slackel 7.7 "Openbox", restricting CPU usage, Haiku improves font handling and software centre performance, Canonical launches MicroCloud |
| • Issue 1045 (2023-11-13): Fedora 39, how to trust software packages, ReactOS booting with UEFI, elementary OS plans to default to Wayland, Mir gaining ability to split work across video cards |
| • Issue 1044 (2023-11-06): Porteus 5.01, disabling IPv6, applications unique to a Linux distro, Linux merges bcachefs, OpenELA makes source packages available |
| • Issue 1043 (2023-10-30): Murena Two with privacy switches, where old files go when packages are updated, UBports on Volla phones, Mint testing Cinnamon on Wayland, Peppermint releases ARM build |
| • Issue 1042 (2023-10-23): Ubuntu Cinnamon compared with Linux Mint, extending battery life on Linux, Debian resumes /usr merge, Canonical publishes fixed install media |
| • Issue 1041 (2023-10-16): FydeOS 17.0, Dr.Parted 23.09, changing UIDs, Fedora partners with Slimbook, GNOME phasing out X11 sessions, Ubuntu revokes 23.10 install media |
| • Issue 1040 (2023-10-09): CROWZ 5.0, changing the location of default directories, Linux Mint updates its Edge edition, Murena crowdfunding new privacy phone, Debian publishes new install media |
| • Issue 1039 (2023-10-02): Zenwalk Current, finding the duration of media files, Peppermint OS tries out new edition, COSMIC gains new features, Canonical reports on security incident in Snap store |
| • Issue 1038 (2023-09-25): Mageia 9, trouble-shooting launchers, running desktop Linux in the cloud, New documentation for Nix, Linux phasing out ReiserFS, GNU celebrates 40 years |
| • Issue 1037 (2023-09-18): Bodhi Linux 7.0.0, finding specific distros and unified package managemnt, Zevenet replaced by two new forks, openSUSE introduces Slowroll branch, Fedora considering dropping Plasma X11 session |
| • Full list of all issues |
| Star Labs |
Star Labs - Laptops built for Linux.
View our range including the highly anticipated StarFighter. Available with coreboot open-source firmware and a choice of Ubuntu, elementary, Manjaro and more. Visit Star Labs for information, to buy and get support.
|
| Random Distribution | 
DragonFly BSD
DragonFly is an operating system and environment designed to be the logical continuation of the FreeBSD-4.x OS series. These operating systems belong in the same class as Linux in that they are based on UNIX ideals and APIs. DragonFly is a fork in the path, so to speak, giving the BSD base an opportunity to grow in an entirely new direction from the one taken in the FreeBSD-5 series.
Status: Active
|
| TUXEDO |
TUXEDO Computers - Linux Hardware in a tailor made suite
Choose from a wide range of laptops and PCs in various sizes and shapes at TUXEDOComputers.com. Every machine comes pre-installed and ready-to-run with Linux. Full 24 months of warranty and lifetime support included!
Learn more about our full service package and all benefits from buying at TUXEDO.
|
| Star Labs |
Star Labs - Laptops built for Linux.
View our range including the highly anticipated StarFighter. Available with coreboot open-source firmware and a choice of Ubuntu, elementary, Manjaro and more. Visit Star Labs for information, to buy and get support.
|
|
• 
• 
• 
• 
• 
• 
• 
0x969CD4E778C7b6549A2B00e34114e0168c86A542 
