DistroWatch Weekly |
DistroWatch Weekly, Issue 1063, 25 March 2024 |
Welcome to this year's 13th issue of DistroWatch Weekly!
While a lot of the focus on desktop environments in the past few weeks has been on GNOME 46 and Plasma 6, not every distribution is package software on the cutting edge. Some distributions are sticking with stable releases in an attempt to provide a solid, reliable experience. We begin this week with a look at Redcore Linux, a Gentoo-based distribution which provides a pre-configured desktop experience with KDE Plasma 5 and binary package tools. We explore Redcore in this week's Feature Story. Redcore, like its parent, offers a rolling release experience where packages are steadily upgraded over time. In our Questions and Answers section this week we discuss the pace of rolling releases and whether some move notably faster or slower than others. What do you think of the pace of rolling release projects? Let us know in this week's Opinion Poll. In our News section we discuss Debian preparing for its annual Project Leader election while Red Hat starts work on a new NVIDIA driver to replace Nouveau. Plus we discuss more malware being shared in Canonical's Snap store while TrueNAS responds to rumours that its CORE edition will be discontinued. Plus we are pleased to share the releases of the past week and list the torrents we are seeding. We're constantly grateful to our donors for their support and we thank you below. We wish you all a fantastic week and happy reading!
This week's DistroWatch Weekly is presented by TUXEDO Computers.
Content:
|
Feature Story (By Jesse Smith) |
Redcore Linux 2401
Redcore Linux explores the idea of bringing the power of Gentoo Linux to the masses. Redcore is a distribution based on Gentoo's Testing branch which uses a hardened profile by default. It aims to be a very quick way to install a pure Gentoo Linux system without spending hours or days compiling from source code, and reading documentation. To achieve this goal, Redcore provides a repository with pre-built binary packages which receives continuous updates, following a rolling release model.
The latest release of Redcore is version 2401. The list of changes in this version is modest and focuses on three main enhancements. First, Redcore migrates from OpenSSL version 1 to OpenSSL version 3, which will affect components throughout the operating system. Second, PipeWire is now used as the default sound system. Third, the Sisyphus package manager received a number of changes, including a completely rewritten backend. The package manager should now recommend suggestions if it can't find the exact name of a package the user typed on the command line.
Redcore 2401 is available in one edition featuring the KDE Plasma desktop. This edition is provided as a 4.5GB ISO file. The project's download page helpfully tells us Redcore ships with two default user accounts, root and redcore, both of which can be accessed on the live media without a password.
The live media boots to the Plasma desktop. On the desktop we find two icons. One is labelled Ask for Help and the other is marked Install System. A panel is placed horizontally across the bottom of the screen. This panel holds the application menu, quick-launch icons, and system tray. Shortly after the desktop loads a KDE welcome window appears.
The welcome window shows us a series of information screens which introduce us to such ideas as how to find the System Settings panel. We're also told about some key features of KDE, including KDE Connect, Vaults, and KRunner. We're also given the chance to connect to on-line accounts with the NextCloud, OpenDesktop, Google, and ownCloud services supported. The final two pages of the welcome window provide tips for contributing and donating to the KDE project.
The Ask for Help icon on the desktop opens Firefox and connects us with a web-based IRC chat room where we can talk about and get help with Redcore Linux.
Redcore Linux 2401 -- Accessing the on-line help channel
(full image size: 1.7MB, resolution: 1920x1080 pixels)
Installer
Redcore uses the Calamares graphical system installer. The installer begins by asking us to select our preferred language. On this first screen the installer shows us three buttons for accessing support, seeing known issues, and reading the release notes. Clicking any of these three buttons has no effect. The following screens ask us to select our timezone and keyboard layout.
Calamares offers us guided or manual disk partitioning. The manual approach gives us a nice, graphical interface which is fairly easy to navigate. The guided approach takes over all available free space with a single ext4 filesystem. The installer offers us three options for swap space: no swap at all, enough swap space to enable hibernation, or a small swap space. None of these options actually cause a swap partition to be created. I suspected, at the time I was setting up Redcore, that the distribution would use a swap file instead since no second partition was created. The final screen of the installer asks us to make up a username and password for ourselves and then the system copies its files to our hard drive.
The installer took a little longer than usual, but not terribly long and Calamares eventually offered to restart the computer for me.
Early impressions
Redcore boots quickly and presents us with a graphical login screen. We can sign into one of two desktop session options: Plasma running on Wayland or Plasma running on X11. The Wayland session is selected by default. The first time we login the KDE welcome window appears again to highlight the desktop's key features.
While the icon for the system installer is, as expected, not shown on the desktop once we install the distribution, the Ask for Help icon remains, which I appreciate. It's nice to have a life line to the community.
Redcore Linux 2401 -- Exploring the application menu
(full image size: 2.0MB, resolution: 1920x1080 pixels)
I found Plasma to be fairly responsive and I appreciated the classic desktop layout. I wasn't a fan of the default theme though. Plasma is set up to use a black font on a grey background and menus are slightly transparent. This makes it harder to read text, particularly when browsing the application menu.
Hardware
The distribution ran well for me when I was using it in VirtualBox. The system ran smoothly, the Plasma desktop was fairly responsive, and the system was stable. Plasma didn't resize dynamically when the VirtualBox window resized, but otherwise it was a pleasant experience. I found Redcore could boot in either UEFI or Legacy Boot environments.
When I tried running Redcore on my laptop, it was a different story. The live medium could boot on my laptop, but only to a text console. I was unable to get either a Wayland session or an X11 session of Plasma to run on my physical hardware, which appears to be a missing driver issue. This prevented me from running the system installer on the laptop.
Redcore used an unusually large amount of disk space (16GB) for a fresh install, about twice the amount used by most desktop Linux distributions. It also consumed a good deal of RAM. The Plasma Wayland session required 1.1GB of RAM just to sign in and the X11 session required almost as much, weighing 950MB. This puts Redcore on the unusually heavy side of memory usage; in a range usually reserved for full-featured Linux distributions running GNOME sessions.
Earlier I mentioned the installer offers three choices for RAM, but none of them cause a swap partition to be created. I had thought, at the time, Calamares would set up a swap file instead. This was not the case. Redcore does not set up any swap space (on a file, partition, or zRAM) regardless of which swap option we select in the installer.
When I was signed into the Wayland session, which I used most of the time early on, I sometimes ran into small issues. For example, the mouse pointer would sometimes disappear. I could still see the mouse highlight buttons and I could click on buttons, but the pointer wasn't visible. Eventually little glitches like this pushed me to try the X11 session and I encountered no problems or visual glitches while using the Plasma on X11 session.
Included software
Despite its large size on disk, Redcore doesn't ship with many desktop applications, outside the usual collection of KDE software. We're given the Firefox web browser, LibreOffice, and the Okular document viewer. The VLC media player is included along with codecs for most audio and video formats. The Lutris and Steam gaming portals are included. Dolphin acts as the file manager while Gwenview helps us view and perform minor edits on images.
Redcore Linux 2401 -- Running VLC and the Steam gaming portal
(full image size: 1.6MB, resolution: 1920x1080 pixels)
The CUPS printing software is included along with the KeePassXC password manager. Java is installed for us along with the GNU Compiler Collection. GNU's command line utilities are installed and there are local manual pages provided.
Redcore ships with the OpenRC init software and this results in a fast and light start-up process. In the background we find version 6.6 of the Linux kernel.
The distribution now ships with PipeWire as the default sound system and this worked well for me. I had no problems with audio during my week with Redcore. I was a little surprised to find sudo was not installed. We can use su to access the root account and perform administrative actions that way.
Redcore Linux 2401 -- The KDE System Settings panel
(full image size: 1.4MB, resolution: 1920x1080 pixels)
Unlike most implementations of the Plasma desktop, Redcore sets up the System Settings panel to use a single pane with a grid of icons for opening configuration modules. Most distributions these days use a two-pane approach for the settings panel, the way GNOME does. Redcore sticks to the classic grid style which is favoured by Xfce and Cinnamon. I feel like KDE has never really got the two-pane approach working smoothly and found Redcore's dedication to the single pane approach was more comfortable, more natural feeling.
Redcore is almost unique in shipping with the OpenSnitch firewall utility installed (though not running) by default. OpenSnitch, which I've talked about previously, is a real-time, application level firewall which will alert us when applications try to access the network. We can then block or allow network connections which OpenSnitch can remember, learning what is acceptable to have communicating over the Internet. I like OpenSnitch and find it's a tool many people, especially Windows users, appreciate for filtering network traffic.
Redcore Linux 2401 -- Blocking network traffic with OpenSnitch
(full image size: 630kB, resolution: 1920x1080 pixels)
Software management
Redcore ships with a few tools for package management. The distribution offers its custom command line package management tool which is called Sisyphus. There is also a graphical front-end for Sisyphus called, appropriately enough, Sisyphus GUI. I also found the Discover software centre is installed. Let's take a look at these one at a time.
Sisyphus GUI is a low level package manager which displays rows of packages. Each row contains the package's name, category, version, and a very short description. We can browse the entire list of packages or search for items by name. To install or remove a selected item we click on a package and then click the Install or Remove button at the bottom of the window. When we click one of the action buttons there is no confirmation or indication of the dependencies we may need, Sisyphus GUI just triggers the addition or removal of the selected package. This worked well enough. I find Sisyphus a little slow compared to other package managers, but functional.
I did notice that Redcore's (and by extension, maybe Gentoo's) repository was missing some key items, particularly multimedia applications. Searches for Rhythmbox, Celluloid, and a few others returned no results.
Sisyphus GUI has a button to trigger an update of the entire operating system. This action also kicks off immediately without any summary of the work it will do or how many packages need to be fetched. The GUI tool then dumps the console package manager's output into its window with no indication of how much progress it has made or how much time is remaining. The GUI tool then appeared to finish - output stopped, with what looked like a message indicating 0 of 333 jobs were remaining. However, the GUI didn't return control to me, it just sat, apparently locked up, not accepting input. In the status bar the application continued to display "I am upgrading the system", but nothing was happening and there was no disk activity. Eventually, I closed the window.
When I switched to trying Sisyphus on the command line it worked okay. The output is a bit terse and some actions run slower on Sisyphus than they do when using APT or pacman, but the add, remove, and update processes all worked. When I performed a global system upgrade I believe I discovered why the GUI tool locked up. There is a pause where the console version of Sisyphus pauses and reports how many updates it will perform and then waits for permission to proceed. The GUI doesn't show this prompt and it makes me think that is why the graphical utility seems to simply hang.
Redcore Linux 2401 -- Exploring the Discover software centre and Sisyphus GUI
(full image size: 1.0MB, resolution: 1920x1080 pixels)
When I first opened the Discover software centre the application appeared to not be working at first. No software was listed in any category and the Home/Featured page showed nothing. When I checked the Updates page no packages were listed. I tried refreshing the package database and still nothing was shown. On the Settings page I found a section for managing repositories and found that, apart from a firmware repository, there were no package sources, which would explain the lack of applications listed.
In the Discover Settings tab there is a button for adding access to the Flathub repository. I clicked it and nothing seemed to happen for a minute, but then Flathub appeared as a new repository on the Settings page. From then on applications showed up in Discover's categories and I was able to fetch Flatpak packages through Discover.
Something which struck me as odd is Discover seems to exist on Redcore solely to work with Flathub. There is even a convenience button to enable the Flathub repository for us. Which makes me wonder why, if Discover is only there to access Flathub, why the repository isn't enabled automatically for us? It seems odd the user needs to hunt for and click a button just to enable the software centre's only function.
Conclusions
When using Redcore I found myself quietly dividing my impressions into three categories: how Redcore performed on its own, how Redcore might improve the experience for someone interested in Gentoo, and how Redcore compared against other mainstream distributions.
On its own, Redcore performs fairly well these days. The shift to PipeWire went smoothly, I really like the OpenSnitch application, and there is enough software installed by default to be useful right away. There are a few issues, like Calamares failing to set up swap space, the Wayland session doesn't quite feel ready to be the default yet compared to X11, and Sisyphus GUI has some rough edges. However, most of my day to day usage of Redcore went well. Firefox and LibreOffice are present, the Sisyphus package manager worked well for me, and I was able to work with minimal fuss or distractions.
For people who like the idea of running Gentoo, Redcore mostly acts as a way to quickly get started. With Redcore we don't need to worry about compiling anything or dealing with Gentoo's "stages". We can just fire up the live medium, install the distribution with a few clicks, and get started. Afterwards we can use Gentoo's Portage or Redcore's Sisyphus to gain access to Gentoo's famous flexibility.
In short, Redcore offers some clear convenience when compared to Gentoo and it functions well - not perfectly, but well. Where I find the distribution suffered, in my eyes, was when I compared it against other mainstream Linux distributions. Redcore is larger (on disk and in memory) than most other Linux projects while including fewer applications. Its package manager is slower, its installer less polished, and its default desktop session has a few more glitches. The theme tends to have less contrast and, while OpenRC makes the boot-up process super fast, the desktop performance once we get signed in is just average. The trouble I had with Redcore not starting a desktop session on my laptop was also unusual as most distributions run a desktop environment without complaint on the same hardware.
In short, I feel Redcore Linux is a fairly capable operating system. It covers the basics and mostly works well. It's certainly more straight forward to set up than vanilla Gentoo. However, when we place Redcore next to larger projects, like Linux Mint, MX Linux, or openSUSE we start to notice little cracks in the armour, little rough patches. Not that Redcore is doing badly, but these other projects have more resources and have smoothed out areas Redcore hasn't yet.
With this said, I think Redcore has evolved over the years. My experience with the distribution gets a bit better every few years whenever I check in with the project and I think it is getting very close to the point where I could recommend it alongside other mainstream distributions. It's certainly the best Gentoo-based experience I have enjoyed to date.
* * * * *
Hardware used in this review
My physical test equipment for this review was an HP DY2048CA laptop with the following
specifications:
- Processor: 11th Gen Intel(R) Core(TM) i5-1135G7 @ 2.40GHz
- Display: Intel integrated video
- Storage: Western Digital 512GB solid state drive
- Memory: 8GB of RAM
- Wireless network device: Intel Wi-Fi 6 AX201 + BT Wireless network card
* * * * *
Visitor supplied rating
Redcore Linux has a visitor supplied average rating of: 8/10 from 31 review(s).
Have you used Redcore Linux? You can leave your own review of the project on our ratings page.
|
Miscellaneous News (by Jesse Smith) |
Debian Project Leader election begins, Canonical's Snap store serves more malware, Red Hat working on new NVIDIA driver, TrueNAS plans for 13.3 CORE launch
The Debian project has announced the start of the campaign for the role of Debian Project Leader. The annual vote will take place in April. This year there are two candidates: Andreas Tille and Sruthi Chandran. Their platforms will be presented on the Debian website, with voting taking place from April 6th to April 19th. Tille's campaign focuses on lowering barriers for developers and reaching out to the next generation of Debian contributors in order to keep Debian's membership healthy and the project relevant. "I will try to establish contact with other distributions. From derivatives, I would like to create some kind of wish list for what we, as their upstream, could do better or what we possibly can learn. I also plan to talk to distributions with different technical bases like Arch Linux, Fedora, openSUSE, Nix, etc., to see whether we can learn from them to solve problems in terms of organization of work and infrastructure. Maybe we will be able to draw some conclusions, for instance, why Arch wiki is famous for good documentation but wiki.debian.org is not." Chandran has not posted a platform at the time of writing.
* * * * *
A month ago we shared a story about malware being distributed through Canonical's Snap repository. The malware made little effort to hide its nature, calling into question Canonical's vetting processes, or even whether the company has any criteria for allowing new Snap packages to be added to its store. Since then another ten malicious apps claiming to be Bitcoin wallet applications have been discovered in the Snap repository: "As with all these scam application, all it does is ask for a Bitcoin recovery phrase, and with that will likely steal all the coins and send them off to the scammer's wallet. Obviously I didn't test this with a real wallet phrase. When given a false passphrase/recovery-key it calls some remote API then shows a dubious error, having already taken your recovery key, and sent it to the scammer." Additional details can be found in Alan Pope's blog post.
* * * * *
Danilo Krummrich from Red Hat as announced the company has started work on a new video driver for NVIDIA cards. The new driver is written in Rust and is intended to eventually replace the Nouveau open source driver. "With Nova we see the chance to significantly decrease the complexity of the driver compared to Nouveau for mainly two reasons. First, Nouveau's historic architecture, especially around nvif/nvkm, is rather complicated and inflexible and requires major rework to solve certain problems (such as locking hierarchy in VMM/MMU code for VM_BIND currently being solved with a workaround) and second, with a GSP-only driver there is no need to maintain compatibility with pre-GSP code. Besides that, we also want to take the chance to contribute to the Rust efforts in the kernel and benefit from more memory safety offered by the Rust programming language." Additional information about the new driver can be found in Krummrich's mailing list post.
* * * * *
Following some opinion pieces on various technology websites, such as The Register and OSNews, which indicated the FreeBSD branch of TrueNAS was being discontinued, the TrueNAS team have responded. To date, TrueNAS has maintained multiple editions, including TrueNAS CORE (which is based on FreeBSD) and TrueNAS SCALE (which is Linux-based). Responding to rumours TrueNAS CORE was no longer being developed, Kris Moore stated that iXsystems plans to continue developing the CORE edition: "TrueNAS CORE hasn't been deprecated, and [13.3] is planned to start making a showing in Q2. It will be based upon FreeBSD 13.3 and will provide a way to keep running jails and upstream packages for some time to come. It is still a rock-solid NAS and we're expecting to support it for a long while for that use-case." TrueNAS 13.3 is expected to be released in June and will include new SMART tools and options for working with network UPS tools.
* * * * *
These and other news stories can be found on our Headlines page.
|
Questions and Answers (by Jesse Smith) |
How slowly can a rolling release upgrade?
Slowing-things-down asks: How frequently must a rolling distribution be upgraded to keep its rolling label? As far as I can tell, being "rolling" is about the method of upgrading, not about the frequency. The rolling method is just a common way of getting recent versions. In theory a rolling distro might be extremely stable by upgrading rarely, providing the best of both worlds - stability and updates. Are there slow moving rolling releases?
DistroWatch answers: You are correct that what defines a rolling release model is the approach to upgrading the system rather than its frequency. A "fixed" release distribution keeps packages at the same version and usually just applies security fixes (and maybe adds new hardware support) during its life time. To get new features the user typically needs to upgrade to the next version of the distribution, which will also remain mostly unchanged for its supported life time.
A rolling release has packages which are upgraded "in place". The old software packages in the distribution's repository are gradually replaced by newer versions of packages. The distribution doesn't pause and get frozen at a fixed point in time, it steadily replaces its old packages with new ones.
While many rolling release distributions strive to stay on the cutting edge of technology, always providing the latest versions of packages, it doesn't need to be this way. There are a few more conservative rolling releases, ones which either upgrade more slowly or which stick to long-term support versions of upstream software to provide a more gradual rolling experience.
The PCLinuxOS distribution is a great example of this slower release approach. The project tends to stick with older, more tried and true software. It also tends to adopt new versions more slowly and carefully, providing a more stable experience for its users. Recently the openSUSE project has been experimenting with a new rolling branch called Slowroll. The Slowroll branch is intended to provide a more conservative rolling release compared to openSUSE's faster moving Tumbleweed branch: "Slowroll is a new experimental distribution from 2023 based on Tumbleweed, but rolling slower. With big updates every one or two months, and continuous bug fixes and security fixes as they come in."
The Void distribution also strives to provide a more stable rolling release experience rather than staying on the cutting edge of technology: "Void focuses on stability, rather than on being bleeding-edge. Install once, update routinely and safely."
* * * * *
Additional answers can be found in our Questions and Answers archive.
|
Released Last Week |
Regata OS 24.0.0
Josué Vicente has announced the release of Regata OS 24.0.0, a major update of the project's openSUSE-based distribution with focus on desktop and gaming needs. This version introduces the recently-released KDE Plasma 6: "The Regata OS 24 'Arctic Fox' is now available for download. This update brings the new KDE Plasma 6 graphical environment and more improvements and fixes to applications. Under the hood, the users will find Linux kernel 6.7, which is combined with Mesa 24 to better support new hardware. To further improve the user experience, Regata OS applications have also received some visual changes, including improvements to the dark theme, rounded corners and other changes to the color scheme. Additionally, OnlyOffice is now installed by default. This office application suite comes with all the essential features and can be used to create text documents, spreadsheets, presentations, PDF files and forms. The KDE Plasma 6 is the newest series of the popular Linux graphics environment. This is a launch that has a flurry of changes, improvements and new features." See the release announcement for further information and screenshots.
Regata OS 24.0.0 -- Running KDE Plasma 6
(full image size: 2.1MB, resolution: 2560x1600 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,978
- Total data uploaded: 44.2TB
|
Upcoming Releases and Announcements |
Summary of expected upcoming releases
|
Opinion Poll (by Jesse Smith) |
Do you prefer a fast or slow rolling release?
In this week's Questions and Answers column we talked about the speed of upgrades in rolling release distributions. Some projects, such as Arch Linux move quite quickly while PCLinuxOS and openSUSE's Slowroll move at a more gradual pace. Which of these approaches do you prefer?
You can see the results of our previous poll on purchasing physical media in our previous edition. All previous poll results can be found in our poll archives.
|
Do you prefer fast or slow rolling releases?
I like being on the cutting edge: | 595 (32%) |
I like slow and steady: | 675 (37%) |
I do not use a rolling release: | 575 (31%) |
|
|
Website News |
Donations and Sponsors
Each month we receive support and kindness from our readers in the form of donations. These donations help us keep the web server running, pay contributors, and keep infrastructure like our torrent seed box running. We'd like to thank our generous readers and acknowledge how much their contributions mean to us.
This month we're grateful for the $255 in contributions from the following kind souls:
Donor |
Amount |
Jerry B | $100 |
Victoria Z | $10 |
J S | $50 |
Mitchell | $50 |
Sam C | $10 |
Brian59 | $5 |
Chung T | $5 |
Darkeugene7896 | $5 |
DuCakedHare | $5 |
Surf3r57 | $5 |
J.D. L | $2 |
PB C | $2 |
Peter M | $2 |
c6WWldo9 | $1 |
Stephen M | $1 |
Shasheen E | $1 |
William E | $1 |
* * * * *
DistroWatch database summary
* * * * *
This concludes this week's issue of DistroWatch Weekly. The next instalment will be published on Monday, 1 April 2024. Past articles and reviews can be found through our Weekly Archive and Article Search pages. 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)
|
|
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$20) |
|
|
|
bc1qxes3k2wq3uqzr074tkwwjmwfe63z70gwzfu4lx lnurl1dp68gurn8ghj7ampd3kx2ar0veekzar0wd5xjtnrdakj7tnhv4kxctttdehhwm30d3h82unvwqhhxarpw3jkc7tzw4ex6cfexyfua2nr 86fA3qPTeQtNb2k1vLwEQaAp3XxkvvvXt69gSG5LGunXXikK9koPWZaRQgfFPBPWhMgXjPjccy9LA9xRFchPWQAnPvxh5Le paypal.me/distrowatchweekly • patreon.com/distrowatch |
|
Extended Lifecycle Support by TuxCare |
|
Reader Comments • Jump to last comment |
1 • Since the demise of Sabayon (by Heinrich on 2024-03-25 00:44:16 GMT from United States)
Redcore seems to be one of the few Gentoo-based distros left after the demise of Sabayon.
2 • Redcore - did it install or not? Confused (by Andy Prough on 2024-03-25 01:36:47 GMT from United States)
@Jesse said, >"When I tried running Redcore on my laptop, it was a different story. The live medium could boot on my laptop, but only to a text console. I was unable to get either a Wayland session or an X11 session of Plasma to run on my physical hardware, which appears to be a missing driver issue. This prevented me from running the system installer on the laptop."
You seemed to be saying here that it didn't install, but then you seemed to do a full review of the installed system. Were you just reviewing the vbox installation? Or maybe I'm reading it wrong?
3 • Rolling releases fast and slow. (by Bobbie Sellers on 2024-03-25 03:47:13 GMT from United States)
The comment calls PCLinuxOS a slow Rolling Release. I would rather call it a steady Rolling Release. Since it is a smaller project it takes a little longer when a problematic piece of software from the Kernel to the Desktop Manager comes along. Most of the users want to keep using their computers under PCLinuxOS and problems happen and are unavoidable in any release as we see so often in the fine reviews of the latest versions of the most interesting distributions. Some people upgrade slowly and do not stay in close touch with the Forum where announcements are made about problems that may arise. That may give them some problems.
So generally the well-informed just keep Rolling along.
bliss- Dell Precision 7730- PCLOS 2024.03- Linux 6.6.22-pclos1- KDE Plasma 5.27.11
4 • slow rolling releases (by user on 2024-03-25 04:54:38 GMT from Hungary)
I have found too that not so speedy rolling as Void has better use cases than the top speedy ones as Arch or Tumbleweed. Similar to the car gears, where 5th gear is more frequently used than the 6th and the speed is optimal and safer for the journey.
5 • Did you fully install Redcore? (by Dan on 2024-03-25 10:00:46 GMT from United Kingdom)
@Jesse
So did you get to test a full installation or Redcore with desktop on physical hardware?
6 • Redcore (by DachshundMand on 2024-03-25 10:16:25 GMT from United Kingdom)
I was installing Redcore and I found that buttons on the first page of the installer did not work I would probably give up thinking that if the developers cannot make the installer work OK then what else is wrong.
7 • Do you prefer fast or slow rolling releases? (by James on 2024-03-25 10:39:06 GMT from United States)
I use Sparky semi-rolling, so voted slow and steady.
8 • Slow moving rolling release (by Kazlu on 2024-03-25 11:02:46 GMT from France)
I would add Manjaro in the list of slow rolling releases. It's actually the whole point of the distro, materialized in its branches: unstable is synced with Arch (and then Manjaro specific modifications are put there), then packages move to testing and finally to stable. They say a package typically takes about two weeks to reach the stable branch.
To me, that looks fine. The only problem I have with this (and potentially other slow rolling distros) is that it is unclear if there is a shortcut path for security patches. If a vulnerability is patched, I don't want to wait 2 weeks to get it. However it's perfectly fine for features. At least I did not find the information so I remain uncertain.
OpenSUSE slowroll is clear about this.
9 • PCLinuxOS (by ThomasAnderson on 2024-03-25 11:29:27 GMT from Australia)
Does pclinuxos provide the option to encrypt /home or the entire drive during installation?
Redcore looks good, if only, the ption was there to select your desired desktop like in OpenSuse.
Personally i can't stand KDE.
10 • Canonical Inclusiveness (by Otis on 2024-03-25 12:19:04 GMT from United States)
That in the News section about Canonical practicing inclusion to the point of propagating the thievery of malware along with its other software is heartening. I'm feeling much better now about stealing that 10 cent Mutt & Jeff comic from the local market when I was 8 years old.
11 • Canonical snap malware (by Alessandro di Roma on 2024-03-25 12:30:06 GMT from Italy)
Once upon a time I used Xubuntu, after snap I switched to Debian XFCE edition, and I'll never go back!
12 • Slow moving rolling release (by Mu on 2024-03-25 12:46:59 GMT from Germany)
@8
Manjaro has a graphic on their site explaining security fixes get "fast-tracked". They at least mention firefox getting fast-tracked this way.
13 • Rolling Releases (by steveo314 on 2024-03-25 14:09:56 GMT from United States)
I've used Debian Sid since 2007 more or less. The only time it isn't bleeding edge is the couple months they are in a hard freeze when they are trying to get a stable release out.
14 • Redcore (by Antonio on 2024-03-25 16:23:20 GMT from Belgium)
I did notice that Redcore's (and by extension, maybe Gentoo's) repository was missing some key items, particularly multimedia applications. Searches for Rhythmbox, Celluloid, and a few others returned no results. Rhythmbox(https://packages.gentoo.org/packages/media-sound/rhythmbox) and Celluloid(https://packages.gentoo.org/packages/media-video/celluloid) are in Gentoo's repository. Maybe they're not available(pre-built) in Sisyphus repôsitory.
15 • PCLinuxOS (by David on 2024-03-25 17:15:38 GMT from United Kingdom)
@9 Yes, you can encrypt /home at installation. And if you don't like KDE Plasma, there are installation media for Mate and Xfce available.
16 • What, exactly, is a 'slow rolling release'? (by R. Cain on 2024-03-25 18:34:18 GMT from United States)
From the poll--
"DO YOU PREFER FAST OR SLOW ROLLING RELEASES?"
Please define--VERY SPECIFICALLY--the difference between a "slow rolling release" and the fad of most distro developers which consists of absolutely having to generate a 'new', faster, more-bloated, buggier, more-feature-filled release than the last one they cranked out just six months ago...and six months before that...and six months before... And of course, all the bugs generated by this frenetic pace are still there, and can't, aren't. and never will be fixed, because the developers are too busy working on the next fastest, biggest , most feature-filled... Don't even waste your time submitting a "bug report". When they don't even have time for the very basics of thorough validation testing and Q-A, distro developers have no time to be bothered with responding to bug reports
Here's a good question for you: why do you even WANT a developer to attempt to generate a truly good, thoroughly 'vetted', brand-new semi-annual distribution when you know, as a critically-thinking technical person that it simply cannot be done?
17 • Posting a platform (by RoestVrijStaal on 2024-03-25 20:08:46 GMT from The Netherlands)
> Chandran has not posted a platform at the time of writing.
"Posting a platform" sounds like it takes some effort though :-)
18 • Semi-rolling (by Ed on 2024-03-25 22:18:22 GMT from Sweden)
I think most users are best served by semi-rolling distributions like Fedora, PcLinuxOS or Opensuse Slowroll. Especially on the desktop/laptop.
Going full-rolling like Arch or Opensuse Tumbleweed is not for everybody and necessitates deep knowledge and experience of fixing problems when they arise.
I just want to use my computer and not being perpetually concerned with potentially disruptive problems arising after a update.
I also dont want to use software that is very old and therefore I no longer use Ubuntu LTS or Debian Stable. My needs is hitherto best catered to by Fedora.
19 • @18 fedora (by Hoos on 2024-03-26 01:49:19 GMT from Singapore)
Fedora is not semi or slow rolling, since you have to change repositories to get to the new release. In my opinion anyway.
It is a fixed release distro with a great release upgrade path. I think this works better in fedora than doing the same in ubuntu or Debian based distro. The Fedora tool/specific commands for this do a pretty good job of clearing cruft in the midst of the release upgrade.
20 • Prefer rolling releases (by Dave on 2024-03-26 01:55:59 GMT from Australia)
For desktops, I like rolling releases for the simple fact there are never any "distro major version" upgrades, where things often go wrong and fail. Not having to worry about version numbers, code names, repo versions, update vs upgrade etc.
I also like getting new versions of software, at least relatively quickly, rather than waiting for years.
21 • Debian wiki (by a on 2024-03-26 04:21:03 GMT from Brazil)
"why Arch wiki is famous for good documentation but wiki.debian.org is not"
Even though I am a big fan of the Debian distribution, I can list three notable points why its wiki is not so acclaimed, namely:
- The distribution's homepage does not contain a visible link to the wiki. In comparison, the Archlinux homepage returns four results with the `ctrl+f wiki` command, while Debian returns none; - The Archlinux wiki homepage has a section for interacting with it, teaching how to read, navigate, contribute, and edit. There is nothing equivalent on the Debian wiki homepage; - Search engines typically display the Archlinux wiki before the Debian wiki.
22 • 18 • Semi-rolling (by Ed...from Sweden) (by R. Cain on 2024-03-26 16:58:45 GMT from United States)
"...I just want to use my computer and not being perpetually concerned with potentially disruptive problems arising after a update...."
-----------------------------------------------------
"...The Year of Linux is the year that you look at your distribution, compare to the year before, and you have that sense of stability, the knowledge that no matter what you do, you can rely on your operating system. Which is definitely not the case today. If anything, the issues are worsening and multiplying. You don’t need a degree in math to see the problem. I find the LACK OF CONSISTENCY to be the public enemy no. 1 in the open-source world. In the long run, it will be the one deciding factor that will determine the success of Linux. Sure, applications, but if the operating system is not transparent, people will not choose it. They will seek simpler, possibly less glamorous, but ultimately more stable solutions, because no one wants to install a patch and dread what will happen after a reboot. It’s very PTSD. And we know Linux can do better than that. We’ve seen it. Not that long ago..."
https://www.ocsmag.com/linux-2017-the-road-to-hell/
23 • Debian Wiki (by JeffC on 2024-03-26 18:34:27 GMT from United States)
One big problem with the Debian wiki is that many pages are written referencing Debian four or more versions ago.
The Arch wiki is kept up to date, the Debian wiki seems to be a forgotten relic of bygone days.
24 • Regata OS 24 (by falcon52 on 2024-03-26 19:55:28 GMT from United States)
I've tried Suse on may occasions and never kept it around very long. I took a chance and loaded Regata on several computers and kind of liked it. However the latest update broke every installation and rendered the keyboards useless. I couldn't even enter my password on the login screen. This is on Intel, Gigabyte, ASUS motherboards and Intel, Radeon, and nVidia video cards, so it's not specific to the hardware.
25 • stability and docuemntation (by Daleep on 2024-03-27 00:59:17 GMT from New Zealand)
@22 - I think most users want things to improve but not drastically change. Windows 10 and now 11 throw that under the bus, so do many Linux distros and desktops (eg Gnome, KDE/Plasma). To re-iterate, improvement is good, crazy change because the 23 yo dev discovered a new drink at the bar is not.
@23 - this is a huge online problem when you run into issues on anything. "Advice" on PHP, C, Python, bash or distro configuration ... bring up 10 year old and often older results in the search. The *overflow sites are horrid - often ignore the problem, assume a solution ot position, or blankly state its a known issue. Unhelpful. I even got an AI to spew up some donkey advice quoting stackoverflow the other day - AND it missed the point, spewing irrelevant drivel. Docs should be kept up to date, and the search engines should pull their socks up and link to that new info, not the internet archive or mirrors.
my 2c
And soon, we have Ubuntu 24.04 N.N. which is an LTS release, so will form a base for Mint and many more for years to come. And, ...Gimp 3.0 sometime after May, maybe?
26 • @12 Manjaro fast-tracked updates (by Kazlu on 2024-03-27 08:41:14 GMT from France)
This is interesting. But even with the term you are giving me, I *still* cannot find it on their website! It seems important, it should be mentioned somewhere. Why burry this in some obscure place in their website? Anyway, if someone can point me to an informative page about this I would appreciate it.
27 • RELIANOID (by Geo. on 2024-03-27 12:54:06 GMT from Canada)
RELIANOID said "The HTTP farms parser has been fortified to improve robustness, and good practices have been applied across the core codebase to achieve Critic Level 4 compliance"
Google replied "there aren't many great matches for your search Try using words that might appear on the page you’re looking for. For example, "cake recipes" instead of "how to make a cake."
🙃
28 • Python debacle (by ThomasAnderson on 2024-03-28 01:12:36 GMT from Australia)
Slightly off-topic but relevant consiering the Github poisoning of many python packages not just in the last week but this seems to be an ongoing issue also last year and before that
Considering the scope and severity of the poisoning of python and pypi packages with malware, we should really ensure that the python packages installed by default are actually malware free, but worse still is that many linux apps use python dependencies which could be poisoned.
I noticed also that if i try to uninstall python from my linux it will break the system, the desktop, mate, gnome etc.
Perhaps python is not necessary for a headless install but if you run a desktop it seems we must have python installed.
How can we trust our install with all the malware poisoning going on? How can we trust any app that we run on our system that uses python? It seems like a security nightmare with no way out.
Thoughts?
29 • @28 • Python debacle (by Geo. on 2024-03-28 13:34:20 GMT from Canada)
"I noticed also that if i try to uninstall python from my linux it will break the system, the desktop, mate, gnome etc."
Yikes! 😲 That's a very bad thing.
30 • @28 Python debacle (by Jan on 2024-03-28 15:46:51 GMT from The Netherlands)
"I noticed also that if i try to uninstall python from my linux it will break the system, the desktop, mate, gnome etc."
Does (Ghost-)BSD also suffer from this Python-problem?
AntiX has a differrent DE, possibly no problem?
31 • a (by Computing debacle on 2024-03-28 17:41:40 GMT from Brazil)
@28 "How can we trust our install with all the malware poisoning going on? How can we trust any app that we run on our system that uses python? It seems like a security nightmare with no way out."
The same way you trust the Internet (the biggest vector for malware proliferation).
47 • Python debacle (by ThomasAnderson on 2024-03-28 23:28:45 GMT from Australia)
So apparently, Linux desktop is dependent upon Python.
Remove of all python apps means breaking your installation.
There seems to be no workaround as most of the linux system uses python scripts and many packages also use python.
How did this become the norm? Now because of this malware poisoning happening on Github of python packages, in essence, the entirety of linux's security is put into question.
There is no way, any person can manually check and verify each and every dependency used in a base install.
Even secure distros like Tails, or Whonix, of Cubes, all use python.
This is almost like the famous compiler trust problem (reflections on trusting trust, by ken thompson), but, not in the same way as Linux actively chooses to use python, for stictching together a working distro wheeras a different approach or programming language could be used.
48 • Python (by Checker on 2024-03-28 23:39:37 GMT from Canada)
@47 > So apparently, Linux desktop is dependent upon Python.
it is not.
> Remove of all python apps means breaking your installation.
Only on distributions which make Python a dependency of their base system, usually as part of a meta package.
> There seems to be no workaround as most of the linux system uses python scripts and many packages also use python.
Some Linux systems do, some don't. You can just use a distro which doesn't rely on Python if you're worried.
> How did this become the norm?
It didn't. You're misunderstanding the situation.
> Now because of this malware poisoning happening on Github of python packages, in essence, the entirety of linux's security is put into question.
This makes no sense. Your Linux distro isn't pulling in Python packages from GitHub.
> This is almost like the famous compiler trust problem
It's not. There isn't anything hidden here. You can just download Python scripts and read them if you want.
> Linux actively chooses to use python, for stictching together a working distro wheeras a different approach or programming language could be used.
Linux is not a uniform family of distributions. Different distributions use different tools and languages. If you have a grudge against Python then use a distro which doesn't include it.
49 • Python debacle (by ThomasAnderson on 2024-03-29 00:16:20 GMT from Australia)
@48
Open your package manager, select all the python installed programs and try to uninstall it without breaking your desktop.
Let me know how that goes.
BTW, Anaconda, which is the installer for RHEL, CentOS, Fedora, Oracle Linux, and Scientific Linux, is written in Python as are yum and dnf which are the package managers. They also require Python to function. Portage, which is the package manager for Gentoo, is also written in Python.
A lot of the modern system management functionality In RHEL requires Python. One example is firewall-cm.
>You can just use a distro which doesn't rely on Python if you're worried. -- name one......
>This makes no sense. Your Linux distro isn't pulling in Python packages from GitHub. -- you fail to graps the issue. The distros did infact pull those packages from Github to build the distro
>It's not. There isn't anything hidden here. You can just download Python scripts and read them if you want. -- are you not understanding the recent issues with malware infestations in python and pyipi? They were using extremely obuscated code to hide their malware which would be impenetrable to the average user to see even if they went line by line through that pythons program code
>Linux is not a uniform family of distributions. Different distributions use different tools and languages. If you have a grudge against Python then use a distro which doesn't include it. -- again, name one...any that doesn't use Python or which is not broken upon removing python
50 • Rolling release (by White_Wolf on 2024-03-29 10:04:20 GMT from Poland)
Solus is perfect as a rolling release. They always step behind bleeding edge so all is stable and almost latest.
51 • Python (by Otis on 2024-03-29 15:37:36 GMT from United States)
@47 @48 etc the only two distros I can find reported as not using python are DamnSmall and TinyCore.
But all I did was google "list distros without python."
52 • RedHat/Fedora security issue (by Dave Postles on 2024-03-29 17:23:20 GMT from United Kingdom)
https://www.redhat.com/en/blog/urgent-security-alert-fedora-41-and-rawhide-users
53 • Python (by Python Dev on 2024-03-29 20:47:44 GMT from Canada)
@49: "BTW, Anaconda, which is the installer for RHEL, CentOS, Fedora, Oracle Linux, and Scientific Linux, is written in Python as are yum and dnf which are the package managers. They also require Python to function. Portage, which is the package manager for Gentoo, is also written in Python."
it seems you are really focused on Red Hat and RHEL-based clones. Maybe step outside of the Red Hat ecosystem?
" you fail to graps the issue. The distros did infact pull those packages from Github to build the distro"
I understand the issue you're saying exists. What I'm saying is I don't think it exists. Can you point to any distributions which ship known malware in Python packages?
"again, name one...any that doesn't use Python or which is not broken upon removing python
Not sure why you're not doing your own research. But, okay, off the top of my head? I think you could do just fine with Puppy, Slackware, Tiny Core, probably Alpine, maybe Void. I don't think any of Arch's core relies on Python either. Basically once you step outside of the commercially backed Linux distributions, Python becomes less common and it either isn't included or you can remove it without breaking anything.
54 • @49 Python and distros (by Andy Prough on 2024-03-29 21:10:34 GMT from United States)
> "you fail to graps the issue. The distros did infact pull those packages from Github to build the distro"
a) No distro was pulling those malware infested packages, because they are fake python packages with altered names of real packages. If you can find a single distro that was pulling incorrectly named fake python packages from GitHub and packaging them in their repos without first inspecting them then you should come back and report it to us. You won't find any.
b) The malware in the fake Python packages was targeting Windows systems, so even if you do find a distro that somehow moronically downloaded incorrectly named fake Python packages from GitHub, they would have no effect on a GNU/Linux distro or any other non-Windows OS.
55 • Python debacle (by ThomasAnderson on 2024-03-29 22:33:40 GMT from Australia)
@53 >I understand the issue you're saying exists. What I'm saying is I don't think it exists. Can you point to any distributions which ship known malware in Python packages?
-no, but that lack of evidence does not that it isn't happening.
-just today it is discovered that a backdoor was found in the compression utility 'xz' versions 5.6.0 and 5.6.1 which breaks SSH encryption, which was incorporated into Arch (they just released a security alert for it)
-in this case not it is not python, but malware slipped through the cracks even though eyes were on it
-you make a point that the absence of evidence is NOT evidence of absence.
It is not somehow reassuring. The python and pypi poisoning that is happening on Github was on a massive scale. According to Checkmarx, 'The attackers used a combination of malware delivery techniques, from publishing rogue packages to PyPI, the main public registry for Python packages, to setting up rogue repositories on GitHub and using code obfuscation and typosquatting to avoid detection. The compromised credentials gave attackers access to GitHub accounts belonging to developers, which then allowed them to inject a malicious dependency into legitimate repositories. One example was a repository belonging to Top.gg, a Discord bot publishing platform whose community includes over 170,000 users.'
my install has 70 python packages. That requires a lot of eyes to scrutinize code.
Look, even if Alpine, Void, Tiny Core or Slackware don't depend on python (i can't verify this as i haven't downloaded and installed them; I run Devuan) the point I was trying to raise was that there are unecessary attack surfaces in a Linux distro that don't have to be there.
The more apps which are included in a linux distro base install, the greater the attack surface. Python is great because generally, programs or scripts that use python pull in many dependencies from many sources including pypi and thus even though the main python app may be ok, the dependencies may not be,
Reduce the attack surface. Reduce the reliance on python. Be vigilant.
56 • XZ malware (by ThomasAnderson on 2024-03-29 22:50:20 GMT from Australia)
Today, Red Hat warned users to immediately stop using systems running Fedora development and experimental versions because of a backdoor found in the latest XZ Utils data compression tools and libraries.
"PLEASE IMMEDIATELY STOP USAGE OF ANY FEDORA 41 OR FEDORA RAWHIDE INSTANCES for work or personal activity," Red Hat warned on Friday.
"No versions of Red Hat Enterprise Linux (RHEL) are affected. We have reports and evidence of the injections successfully building in xz 5.6.x versions built for Debian unstable (Sid). Other distributions may also be affected."
Debian's security team also issued an advisory warning users about the issue. The advisory says that no stable Debian versions are using the compromised packages and that XZ has been reverted to the upstream 5.4.5 code on affected Debian testing, unstable, and experimental distributions.
57 • rolling releases and xz - my $0.02 (by Brad on 2024-03-29 23:52:59 GMT from United States)
I just logged on to see that there were security updates (from Manjaro stable) for xz. Glad it came through so quickly, and I think this may answer a question from earlier posts about security fixes in Manjaro.
58 • XZ malware (by ThomasAnderson on 2024-03-30 00:05:04 GMT from Australia)
Microsoft software engineer Andres Freund discovered the security issue while investigating slow SSH logins on a Linux box running Debian Sid (the rolling development version of the Debian distro).
-- It was accidentally discovered.
How many have not been discovered?
Number of Comments: 59
Display mode: DWW Only • Comments Only • Both DWW and Comments
| | |
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 1096 (2024-11-11): Bazzite 40, Playtron OS Alpha 1, Tucana Linux 3.1, detecting Screen sessions, Redox imports COSMIC software centre, FreeBSD booting on the PinePhone Pro, LXQt supports Wayland window managers |
• Issue 1095 (2024-11-04): Fedora 41 Kinoite, transferring applications between computers, openSUSE Tumbleweed receives multiple upgrades, Ubuntu testing compiler optimizations, Mint partners with Framework |
• Issue 1094 (2024-10-28): DebLight OS 1, backing up crontab, AlmaLinux introduces Litten branch, openSUSE unveils refreshed look, Ubuntu turns 20 |
• Issue 1093 (2024-10-21): Kubuntu 24.10, atomic vs immutable distributions, Debian upgrading Perl packages, UBports adding VoLTE support, Android to gain native GNU/Linux application support |
• Issue 1092 (2024-10-14): FunOS 24.04.1, a home directory inside a file, work starts of openSUSE Leap 16.0, improvements in Haiku, KDE neon upgrades its base |
• 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 |
• 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 |
Coyote Linux
Coyote Linux Personal Firewall was a personal firewall distribution of Linux designed for the purpose of protecting a personal or educational network. In addition to being designed to have very low hardware requirements, Coyote Linux was able to provide the performance and uptime that was expected from any Linux based system. This firewall product was licensed for personal and educational use and was available free of charge.
Status: Discontinued
|
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.
|
|