 DistroWatch Weekly |
| DistroWatch Weekly, Issue 728, 4 September 2017 |
Welcome to this year's 36th issue of DistroWatch Weekly!
New distributions come along all the time, trying to solve old problems in new ways, improving on a parent distribution or showcasing new applications. This week we begin with a review of Nitrux, a project that is attempting all three. The Nitrux distribution features a custom, Plasma-based desktop environment called Nomad. It also offers a new package manager, firewall configuration tool and custom music player. Our Feature Story explores the details of the Nitrux distribution and its new utilities. In our News section we discuss a new community repository for SUSE Linux Enterprise, remote desktop tools coming to GNOME running on Wayland and an update to Bodhi Linux's installation media. We also cover two new changes coming to the Linux Mint distribution and Manjaro dropping support for 32-bit computers. Then, in our Tips and Tricks column, we talk about the Void distribution's approach to source-based software management. Plus we share the distribution releases of the past week and provide a list of the torrents we are seeding. In our Opinion Poll we ask our readers how important an operating system's package manager is when deciding what distribution to run. Finally, we are happy to welcome the BackSlash Linux project to our database. We wish you all a fantastic week and happy reading!
Content:
- Review: Nitrux 1.0.2
- News: SUSE creates new community software repository, remote desktop tools coming to GNOME on Wayland, Bodhi publishes updated media, Mint rewrites backup tool, Manjaro dropping 32-bit support
- Tips and tricks: Void source packages
- Released last week: Redcore Linux 1708, Emmabuntus 8-1.03, Bodhi Linux 4.3.0
- Torrent corner: 4MLinux, BlackArch, Bodhi, Emmabuntus, IPFire, KaOS, Linux Lite, Live Raizo, Manjaro, ReactOS, Redcore, Sabayon
- Opinion poll: Is the package manager important?
- New additions: BackSlash Linux
- New distributions: Namib GNU/Linux
- Reader comments
Listen to the Podcast edition of this week's DistroWatch Weekly in OGG (68MB) and MP3 (86MB) formats.
|
| Feature Story (by Jesse Smith) |
Nitrux 1.0.2
Nitrux is a fairly new addition to the DistroWatch database. The distribution features a custom desktop environment, called Nomad, which is based on KDE's Plasma 5 desktop. The Nomad desktop reportedly features a simplified system tray and a friendly, graphical front-end for the UFW firewall utility. Nitrux also ships with a custom software manager called NX Software Center and a music player called Babe. The Nitrux project previously featured the Anbox utility for running Android apps on GNU/Linux desktop distributions, but Anbox has been removed in recent versions of the Nitrux distribution.
Nitrux is available in just one edition and is built for 64-bit x86 computers exclusively. Originally I tried to download Nitrux from the project's website and found my download kept getting disconnected partway through. I switched to downloading the project's ISO file (1.0GB in size) from a SourceForge mirror and this download completed successfully.
Booting from the Nitrux installation media brings up a menu asking if we would like to launch the distribution's live mode or start the system installer. Taking the live mode option, we are brought to a graphical login screen. We can sign into the Nomad desktop by using "nitrux" as both the username and password.
The Nomad desktop appears to use KDE's Plasma desktop software, but with a high degree of customization. The main desktop panel containing the application menu and system tray is placed at the top of the screen. A quick-launch bar is displayed at the bottom of the screen. The launch bar at the bottom of the desktop displays icons, but no tool tips or text to indicate what clicking on each icon will open. The application menu is displayed as a large grid of icons. The first page of the menu displays commonly used (or "favourite") applications. The second page lists all installed applications. The desktop's default background is mostly white with red and purple at the corners in shades that remind me of cotton candy.
Nitrux 1.0.2 -- The Nomad desktop and application menu
(full image size: 56kB, resolution: 1280x1024 pixels)
Installing
Looking around the live desktop environment I did not find any launcher for a system installer. I checked the project's website and could not find any documentation on installing the operating system. I rebooted the computer and selected the installation option from the ISO's boot menu. The system installer is one I had not used before. It is a graphical application which begins by asking us to create a new username and password for ourselves. The partitioning screen comes next. Here I was shown a list of partitions, but there wasn't any clear indication of how I should proceed to change disk partitions or assign them to mount points. With some trial and error I found I could click a partition to highlight it and then click a box to assign the partition to a mount point. I could not find any way to create new partitions, so it seems we need to use a separate partition manger (such as GParted) before we begin the installation process.
Once we set up mount points we can choose whether to install a boot loader. Then the installer copies its files to the disk. When the installer finished, I was presented with a mostly blank screen with a quick-launch bar at the bottom and no clear way to shut down the computer or reboot. I used the quick-launch bar to open a terminal and forced a reboot from there.
When I booted into my freshly installed copy of Nitrux I was presented with a login screen. Signing in, I was once again shown the project's system installer with no desktop environment. It seems that when we install Nitrux from the minimal environment that just runs the installer, we end up with an operating system that just provides enough of an environment to launch its installer.
I booted from the installation media once more and went looking through the live desktop environment. I eventually discovered that the system installer is launched from a graphical utility called Systemback which is typically used to backup and restore the operating system. I went through the installation process again and, when I was finished, was presented with a full copy of Nitrux, complete with functioning desktop environment.
Hardware
At least I ended up with a working desktop system when I ran Nitrux inside a VirtualBox virtual machine. When I tried to launch Nitrux on my physical desktop machine the distribution failed to boot. This surprised me as Nitrux is based on Ubuntu, a distribution which tends to work well with my hardware. This left me to experiment with Nitrux in the virtual environment. I found the operating system, when logged into the Nomad desktop, used 480MB of RAM. The desktop environment was sluggish at first, however performance picked up quite a bit after I disabled file indexing and some visual effects from the System Settings panel. Nitrux automatically integrated with VirtualBox and was able to make use of my computer's full screen resolution without any configuration on my part.
Early impressions
Left to explore Nitrux in a VirtualBox environment, I started looking around the Nomad desktop. Nomad's information screens identify it as being based on KDE Plasma 5.10, but the environment looks and acts quite a bit differently than Plasma. For example, applications use a unified menu bar, which is displayed in the panel at the top of the screen. The application menu is a large grid of icons and, unlike the Plasma desktop, Nomad will not allow the menu to be swapped out for alternative menus. An effort appears to have been made to streamline Plasma, removing customization options and alternative widgets.
There are some other odd design choices too. For example the virtual terminal application has a bright blue background. The default fonts tend to have a tall, thin look which I found hard on my eyes after a while.
Nitrux 1.0.2 -- A virtual terminal and the notification area
(full image size: 61kB, resolution: 1280x1024 pixels)
Another problem I ran into is the distribution sometimes displays icons without accompanying text or tool tips. This can leave us somewhat in the dark as to what controls do. For example, when signing out of the Nomad desktop we are presented with a confirmation screen containing four symbols: a line, a circle, a lighting bolt and an arrow. Given the context I was able to work out which button corresponded to a given action (reboot, shut down, logout and sleep) but the lack of accompanying text meant I spent more time interpreting Nomad's screens than would normally be required if text had simply been included. This is an issue that popped up a number of times during my trial and it made using Nitrux feel like using an operating system with a foreign language locale selected.
Another visual problem I ran into was the desktop's top panel would sometimes be invisible when I logged in. I could still click on the panel to open the application menu, but the panel was not drawn on the screen. With a little experimenting I found this was caused by VirtualBox's 3-D support. Disabling VirtualBox's 3-D display feature caused the Nomad panel to always be displayed properly.
Software management
Software management on Nitrux is handled primarily by the NX Software Center. When NX Software Center first opens we are presented with a window containing two buttons near the top. Both buttons look to me to be "Home" buttons, judging by their shape, but there is no text to give them context. The first tab shows a single icon labelled "Core". It is not clear right away whether this is an installed package, an available package or an upgrade as no further information is provided. The second tab shows us a list of categories. Some of these categories are software related, but others do not appear to be. For example, some listed categories are Business, Communication, Developer Tools, Food & Drinks, Games, and Health & Fitness. Clicking a category shows us available packages in the given category. Some of these items are fairly clearly labelled, carrying names like "Investment Viewer" while others are more cryptic, such as the "irpf2017" package. A text field near the top of the window lets us search for specific packages by name.
Nitrux 1.0.2 -- The NX Software Center
(full image size: 257kB, resolution: 1280x1024 pixels)
Clicking on some packages opens up a new page containing a description of the selected package and a screen shot. Other times, clicking on a package does not bring up anything other than a blank page and the words "Other open source". At the bottom of the information screen is an Install button. Sometimes clicking this button causes the selected package to be installed and its icon added to the application menu. Other times, clicking the Install button results in an error simply reporting "not found" and the package is not installed.
Once I had installed a few items I found they were added to the first tab in the NX Software Center so I gather the first tab lists installed items. So far as I could tell, NX Software Center only lets us work with Snap packages, not Debian packages and to work with Debian archives we need to turn to the command line.
Nitrux 1.0.2 -- Browsing available packages
(full image size: 566kB, resolution: 1280x1024 pixels)
Since Nitrux uses Ubuntu repositories (specifically Ubuntu 17.10's repositories), I has expected the distribution to offer APT and apt-get package management tools. However, Nitrux ships with pacapt which is basically a command line program which uses the Pacman package manager's syntax and works with Debian packages. This means that instead of using "apt-get upgrade" to install software updates, we run "pacman -Syu".
While using Nitrux I never saw any indication software updates were available and I had to check for security updates manually. There is no graphical update manager, leaving the user to download security updates from the command line.
Settings
Nitrux uses the KDE System Settings panel to configure the desktop experience. For the most part the settings panel is pretty standard and contains the same configuration modules used by other platforms running KDE software. There are several modules available for changing the look of the desktop, adjusting short-cuts and tweaking visual effects. There is a module for setting up KDE Connect, a service which facilitates communication with Android devices. There is also a tool for enabling and disabling systemd services.
Nitrux 1.0.2 -- The settings panel
(full image size: 111kB, resolution: 1280x1024 pixels)
There were a few odd design choices here too. For example, the tool to create and adjust user accounts is not called "Users", but rather "Account Details". There is no module for setting up printers and scanners. There are three tools listed under the panel's Network category. These three modules are called Connections, Settings, and Connectivity. At first these may seem like three ways of describing the same thing, but upon closer inspection these modules handle setting up network connections, managing proxies and working with Samba shares, respectively.
The Nitrux website makes special mention of the distribution's firewall. The firewall utility is a graphical front-end for the UFW firewall. The custom firewall tool has a fairly simple layout which allows us to create new rules that either deny or allow network traffic. We can fine-tune the rules a bit, selecting source and destination addresses and ranges of ports. The firewall tool works, though I'm not sure if I see a large difference between using it or the more commonly used GUFW front-end for the UFW firewall.
I ran into a couple of issues when trying to print. The first was there is no printer configuration module available. I also found the CUPS printing software is not installed by default. I checked in the Nitrux software manager and could not find any front-end to working with printers or CUPS. I then switched to the command line and installed the system-config-printer package along with CUPS and CUPS drivers. The printer configuration utility was not added to my application menu so I launched it from the command line. CUPS was able to detect my network printer, but attempting to complete the setup resulted in CUPS throwing a vague "Internal error" message and failing to complete the connection to my printer.
Nitrux 1.0.2 -- Trying an alternative look
(full image size: 340kB, resolution: 1280x1024 pixels)
Finally, on the subject of system configuration, there is an application included with Nitrux called Kvantum Manager. This utility offers a quick and easy way to tweak the Nomad desktop environment. These tweaks can help us alter the desktop's theme, improve performance and place text under icons. I was not able to use Kvantum to get rid of the unified menu panel or switch application menus, but I did get a faster desktop with more text to assist in navigating the interface.
Applications
Nitrux does not ship with many applications by default. We are given a few common desktop programs such as the Chromium web browser (without Flash support), the Kate text editor and the Dolphin file manager. The distribution ships with the Babe music player, which I will come back to later, and the VLC multimedia player. Codecs are included for playing common media formats. We are given a PDF viewer, the Ark archive manager and a hardware information browser. Nitrux ships with version 6.3 of the GNU Compiler Collection and the systemd init software. The distribution runs on version 4.11.0 of the Linux kernel.
Earlier I mentioned the Babe music player which appears to be a media player unique to Nitrux. The initial screen Babe greets us with is a bit confusing. Near the top of the window is an empty Sources list. Then there is a plus sign in the middle of the window and a drag-n-drop region on the right. Near the bottom of the window we find an area which I think should allow us to type in a YouTube address and another box where I think we can select the location of extensions. There seem to be several options open to us, but not a lot of familiar-looking controls. I tried the + button first and was given the chance to select a directory where my audio files were kept. I started by selecting a directory with just two audio files. Babe locked up for a few seconds and then displayed an error message which simply read "oops".
Nitrux 1.0.2 -- The Babe music player
(full image size: 276kB, resolution: 1280x1024 pixels)
I next tried dragging audio files from the Dolphin file manager to the drag-n-drop region of Babe's window. The media player appeared to lock up for about a minute while a lot of data was passed over my network connection and then Babe crashed. After this, I switched to using VLC to play audio and video files and found the VLC multimedia player worked well.
Conclusions
Nitrux's motto is "Simple, quick and responsive." During my trial, I felt as though none of those descriptions suited the distribution. With its default settings, the Nomad desktop was not particularly responsive (though it might have been if I had managed to get the distribution running on physical hardware). Nitrux was relatively slow to boot and applications were not particularly quick (or slow) to load.
This is a young project and it has a lot of problems, ranging from hardware compatibility to lack of an update manager, to a software manager that was only able to install packages about two-thirds of the time, to a music player that crashed when asked to play audio files. There is a noticeable lack of documentation and on-screen queues for completing tasks. Perhaps the most obvious example of this lack of guidance comes at install time. I found selecting the Install option from the live media's boot menu would result in the operating system not installing properly. I had to load the live desktop, launch the backup manager and use that to launch the system installer - a process that is as roundabout as it is counter-intuitive.
What really puzzled me about Nitrux is the distribution is based on software that works well with my computer and that I find useful. Nitrux is largely based on Ubuntu and the KDE Plasma desktop, both examples of software that play well with my hardware. Yet Nitrux has its own system installer which is less friendly than Ubuntu's. The desktop is less flexible and slower than Plasma. The software manager does not function as well as Ubuntu's Software Center and cannot work with Debian packages.
I was unhappy with the distribution's approach of removing the APT tools and update manager and replacing them with command-line only tools which use Pacman syntax. Keeping APT and pacapt together might have made sense for appealing to Pacman fans, but stripping APT and its related tools out entirely just crippled package management on the distribution without adding any benefit.
This style of approach seems to be repeated throughout the distribution, replacing working utilities (music player, system installer, software manager, application menu) with alternatives that do not function as well as the ones provided by the parent distribution.
* * * * *
Hardware used in this review
My physical test equipment for this review was a desktop HP Pavilon p6 Series with the following specifications:
- Processor: Dual-core 2.8GHz AMD A4-3420 APU
- Storage: 500GB Hitachi hard drive
- Memory: 6GB of RAM
- Networking: Realtek RTL8111 wired network card
- Display: AMD Radeon HD 6410D video card
* * * * *
Visitor supplied rating
Nitrux has a visitor supplied average rating of: 4.1/10 from 22 review(s).
Have you used Nitrux? You can leave your own review of the project on our ratings page.
|
| Miscellaneous News (by Jesse Smith) |
SUSE creates new community software repository, remote desktop tools coming to GNOME on Wayland, Bodhi publishes updated media, Mint rewrites backup tool, Manjaro dropping 32-bit support
SUSE is working to expand the number of software packages available to its enterprise customers with a new, community run repository. The new software repository is called SUSE Package Hub and is offered as a free add-on for SUSE Linux Enterprise customers. A post on the SUSE blog states: "It's a place where SUSE Linux Enterprise users can go to find a collection of popular open source packages that are pre-built for SUSE Linux Enterprise Server 12, ready to install and use. While the packages from the SUSE Package Hub are not officially supported by SUSE, they are officially approved for use, and you can use these packages with SUSE Linux Enterprise Server without worrying about breaking your SUSE support contract. And even better than Rerun, packages in SUSE Package Hub are free with a valid SUSE Linux Enterprise subscription." New packages can be submitted to the repository by community members and third-party software vendors.
* * * * *
The Wayland protocol is expected to eventually replace the X display server (currently used by most distributions) in the near future. In fact some distributions, such as Fedora, are already using Wayland by default to power the GNOME desktop. One drawback to using the new Wayland technology has been the lack of remote desktop utilities. Thanks to Jonas Ådahl from Red Hat, remote desktop access is coming to GNOME running on Wayland sessions. "GNOME's Vino remote desktop server was left behind when GNOME transitioned their desktop from the X compositor to Wayland. This meant that people who use distributions that stay close to upstream, like Fedora 25, have been left without a working VNC or even an RDP server for almost a full year. Jonas Ådahl from Red Hat has been busy adding new D-Bus APIs to libmutter. Mutter is the GNOME window manager and Wayland compositor. The two new APIs, org.gnome.Mutter.RemoteDesktop and org.gnome.Mutter.ScreenCast, expose a PipeWire stream containing the contents of the system's screens. The new APIs can create full-screen streams, or streams for individual windows. Only the former has been implemented." A post on the Ctrl blog website has further details.
* * * * *
The Bodhi Linux project published a new version, 4.3.0, this week and then quickly published a minor bug-fix release, version 4.3.1. The reason for the quick update was an issue in the default software repository configuration which affected users of Bodhi's Standard edition. "It seems like just yesterday that I was posting about Bodhi 4.3.0. Oh wait, it was just yesterday. In a friendly reminder that I am still human - we had a pretty major issue with one of the Bodhi 4.3.0 discs. Most issues we can simply patch via the package manager after the fact without releasing a new set of ISO images, but this issue was fairly unique. The new system was failing to add the official Bodhi repository to the installed system. Because of this I've published a set of discs with the 4.3.1 version number. You will only be affected by this issue if you installed Bodhi 4.3.0 using the Standard release." People who have already installed Bodhi Linux 4.3.0 can fix the issue themselves by adding the line "deb http://packages.bodhilinux.com/bodhi xenial b4main" to their /etc/apt/sources.list file.
* * * * *
The Linux Mint team has unveiled a few new changes that will be coming to the distribution in the near future. One feature grants applications the ability to share progress information with the desktop environment, which allows a progress bar to be displayed in the task switcher. "When an application is busy doing something it usually shows you a progress bar. Instead of mindlessly looking at the bar and waiting for it to reach 100% people usually seize the opportunity to do something else or distract themselves on the Web while waiting. The problem is.. how do you know when the application is ready if you can't see its progress bar? How can you keep an eye on the progress of the operation after you minimize the window or focus other windows on top of it? Some applications like the USB Stick formatter or the Nemo file operations worked around that problem by changing their window title to indicate their progress. That way their percentage is visible not only on their titlebar but also in the panel window list. Windows 7 did even better, they implemented a mechanism which allows applications to communicate progress to their environment. We decided to make this possible in Linux by implementing it in LibXapp." In addition, the backup utility has been given an overhaul, streamlining the backup process and allowing the backup application to run as a regular user instead of as the administrator. Details on both changes, along with screen shots, can be found on the Linux Mint blog.
* * * * *
Philip Müller has announced Manjaro Linux will begin phasing out support for 32-bit computers in the final quarter of 2017. A post on the Manjaro Linux website has the details: "Due to the decreasing popularity of i686 among the developers and the community, we have decided to phase out the support of this architecture. The decision means that v17.0.3 ISO will be the last that allows users to install 32-bit Manjaro Linux. September and October will be our deprecation period, during which i686 will be still receiving upgraded packages. Starting from November 2017, packaging will no longer require that from maintainers, effectively making i686 unsupported."
* * * * *
These and other news stories can be found on our Headlines page.
|
| Tips and Tricks (by Jesse Smith) |
Void source packages
Last May I reviewed an independently developed Linux distribution called Void. The Void project has a number of unusual characteristics which make it an interesting distribution to follow. Void uses the runit init software rather than the more commonly used systemd and SysV init. Void is a lightweight, rolling release project which uses Flatpak packages to expand its range of available software. Void also uses a custom package manager, the X Binary Package System (XBPS). I talked a bit about these features in my review, but glossed over another significant feature: Void's source-based packages.
Void's source-based packages are handled by a framework that should feel familiar to people who have run Gentoo or one of the BSDs. The source framework - the tools for building Void's source packages and the recipes for turning the source code into executable files - is stored in a git repository and managed by the xbps-src utility. To get started, I recommend reading Void's wiki page on using xbps-src.
To start using Void's source packages, or ports system, we need to install the xtools package and download a copy of the source framework. We can accomplish this with the following four commands:
xbps-install xtools
git clone https://github.com/voidlinux/void-packages
cd void-packages
./xbps-src binary-bootstrap
Note the "./" in front of the xbps-src command. This is required because the xbps-src script is inside the void-packages directory. At this point we have the framework in place to start configuring source packages and building them into installable packages. A list of the available software can be found under the srcpkgs directory. There are hundreds of packages available, so take your time browsing! Each package's meta data, distro-specific patches and configuration settings can be found in a directory named after the package. For example, the information for the VLC multimedia player can be found under srcpkgs/vlc. Each package's directory contains a template file which contains meta information and configuration settings. While we could edit this file directly to change settings, the recommended approach is to use the xbps-src utility to toggle any configuration changes we wish to make.
To see what configuration options are available for a given package we can run xbps-src with the show-options flag. For example:
./xbps-src show-options vlc
We can then turn certain options on or off with the -o flag. For instance the following command disables the Lua option when compiling the VLC media player:
./xbps-src -o ~lua pkg vlc
At this point I feel it is important to stop and address the pkg parameter in the above line. The xbps-src script accepts a number of action commands. The pkg parameter causes Void to build the selected software into a binary package we can install, like a .deb or .rpm archive on other distributions. There are a number of other parameters we can try:
| Command |
Action |
| ./xbps-src pkg vlc |
build a package for the VLC software |
| ./xbps-remove vlc |
deletes the VLC package from the system |
| ./xbps-src list |
displays a list of installed packages |
| ./xbps-src install vlc |
install the VLC software |
Details on the XBPS build process, its stages and options can be found in the xbps manual. I found it to be a helpful document, especially when I was playing around with alternative configurations for packages.
Running the command for building a package, for example: "./xbps-src pkg vlc", will download the necessary dependencies, compile the source code and save the resulting binary package in the hostdir/binpkgs directory. From there we can install the newly created package using the xi command. For example:
xi vlc
The xi command will prompt us for our sudo password if required so the new package can be installed on the operating system.
The documentation mentions we can use the command ./xbps-src install to install software rather than building a package for it. I tried this and the process appeared to complete successfully, but it did not result in the specified software being installed in my path. I checked the documentation and it says the newly built software will be installed in the directory masterdir/destdir/packagename. However, when I looked, my masterdir/destdir directory was completely empty, so I'm not sure where my software went after it was built. After that, I returned to building packages and manually installing them with the xi command.
When we are through with software and want to remove it, we can use the xbps-remove command. For example, to uninstall the Firefox browser we can use
xbps-remove firefox
The above command removes the Firefox browser, but not any dependencies the browser might leave behind. To also clear away package dependencies which are no longer required we can run:
xbps-remove -o firefox
On the whole, I found the xbps-src approach to building source code into packages to be fairly straight forward. The framework seems to be solid and useful. Having direct access to the build recipes as well as easy access to key configure flags certainly introduces a good deal of flexibility into the build process.
I am more familiar with FreeBSD's ports system so I think it's natural I draw some comparisons between the two. One of the big things that stood out for me was that FreeBSD organizes its 27,000+ ports into categories. So a port might be named "www/firefox" while on Void all ports are stored in one directory, so the name of the package is just "firefox". This is more simple and saves us some hunting, but means the srcpkgs directory is likely to get quite large over time.
Another thing I noticed was Void's ports are kept on GitHub where it is easy to submit a new package or an update. FreeBSD takes a more roundabout approach and has people send patches to the bug tracker when a port needs to be submitted or updated. Though I think FreeBSD's tools for handling ports are a bit streamlined in comparison. FreeBSD (and, to a point, Gentoo) limits the number of tools used. On FreeBSD I can checkout the ports framework with one command (portsnap) and perform builds, configuration, installs and removals with another command (make). Void uses four tools: git to checkout ports, xbps-src to build and configure packages, xi to install software and xbps-remove to delete old packages. The effects are the same and the steps approximately the same, but Void uses different tools for different jobs while FreeBSD mostly unifies things under its make utility.
My final comparison is I found the meta-data on Void's packages to be easier to read. I find FreeBSD ports to be somewhat cryptic, even after using (and creating them) for years. Void's template files are quite clear and I was able to read and modify them without requiring any documentation. That was a pleasant surprise and it helped me dive quickly into working with Void's collection of packages.
All in all, I liked Void's approach to working with source builds. It took me a little while to get familiar with the various options, but the result is a powerful collection of tools which give us flexibility when it comes to the features we build into our software.
* * * * *
More tips can be found in our Tips and Tricks archive.
|
| Released Last Week |
Redcore Linux 1708
Ghiunhan Mamut has announced the release of a new snapshot of Redcore Linux, a rolling release desktop distribution based on Gentoo. The new snapshot offers several package upgrades and new fixes. "This release focuses on polishing the overall look'n'feel and out of the box experience of the distribution. New features are still present though. Here is a brief changelog since Redcore Linux 1706: resync with Gentoo stable portage tree (27.08.2017); Linux kernel LTS 4.9.40 with BFQ and UKSM enabled by default; Linux kernel 4.12.x available in the repository, for those who may want to use newer kernels; early CPU microcode updates are now enable by default for both Intel and AMD, this should improve the overall stability; graphics stack updated to mesa 17.1.7, llvm 4.0.1, libdrm 2.4.83, xorg-server 1.19.3; better WIFI connectivity support, Broadcom, Mediatek and Ralink chips should now work out of the box." A complete list of changes can be found in the release announcement. The Redcore Linux installer now requires the target computer has 2GB of RAM and 20GB of hard disk space.
Emmabuntus 8-1.03
The Emmabuntus project has announced the release of an update to the project's Debian-based edition. The new release will probably be the last to be based on Debian 8 "Jessie" as the new version, likely to arrive in September 2017, will be based on Debian 9 "Stretch". "This Debian Edition 1.03 version includes the following fixes and enhancements: Version based on Debian 8.9. Replacement of Icedove by Thunderbird. Replacement of the httpredir repositories by the FTP ones. Replacement of the now obsolete Pipelight and Pepper Flash by Adobe Flashplayer. Replacement of the now obsolete Skype 4.3 by the version 5.3, on 64-bits architecture only. Addition of the Arduino IDE. Addition of a function to change the Dock level within the Xfce menu. Addition of the French and English tutorials to configure a printer." A complete list of changes can be found in the project's release announcement.
Bodhi Linux 4.3.0
Jeff Hoogland has announced the release of a new version of the lightweight Bodhi Linux distribution. Bodhi ships with the Moksha desktop (a fork of Enlightenment) and is available in three flavours: Standard, AppPack (offering more applications) and Legacy (for older computers). The project's release announcement reads: "Today I am pleased to announce the release of Bodhi Linux 4.3.0. This is a normal update release and it comes three months after the release of Bodhi 4.2.0. Existing Bodhi 4.x.y users do not need to reinstall as the primary goal of this update release is to simply keep the current ISO image up to date. This release image includes EFL 1.19.1, Terminology 1.1.0, Ephoto 1.5, and Linux kernel 4.11. As with every release in the 4.x.y Bodhi series it is built on top of the rock solid foundation that is Ubuntu 16.04."
Bodhi Linux 4.3.0 -- Running the Moksha desktop
(full image size: 839kB, resolution: 1280x1024 pixels)
BlackArch Linux 2017.08.30
BlackArch Linux is an Arch Linux-based distribution designed for penetration testers and security researchers. The project has announced the availability of a new snapshot of the distribution. The new ISO image carries the version number 2017.08.30 and the distribution's blog provides the following release announcement: "Today we released new BlackArch Linux ISO images. Here's the changelog: bug fix - strap.sh (removed 'http:' for PGP key server); updated BlackArch installer to version 0.5.2 (update SHA1 sum of strap.sh); include Linux kernel 4.12.8; updated many BlackArch tools; updated all system packages; updated all window manager menus (Awesome, Fluxbox, Openbox). We wish to thank all of BlackArch's users, mirrors, and supporters. Thanks for your help." BlackArch Linux is available in Live and net-install editions. Download options include a live dual-layer DVD image or a single-CD network installation ISO.
Linux Lite 3.6
Jerry Bezencon has announced a new release of Linux Lite, a beginner friendly Linux distribution based on Ubuntu and featuring the Xfce desktop environment. The new version, Linux Lite 3.6, makes it easier to select nearby software sources for faster downloads and includes a new way to search through documentation. "Linux Lite 3.6 Final is now available for download. There have been a number of changes since the 3.4 release. In this release, we introduce two major new features. Firstly, Lite Sources is a repository selector that allows you to easily select a software repository nearest to you. When new versions of Linux Lite branded applications are released, you'll now get much faster download speeds thanks to Lite Sources. The second newest feature for Linux Lite 3.6 is the inclusion of both an on-line and off-line search engine for the Linux Lite Help Manual. Search results are highlighted to allow you to easily find the help content you need fast." Details on how to use these features, along with screen shots, can be found in the project's release announcement.
Linux Lite 3.6 -- Running the Xfce desktop
(full image size: 307kB, resolution: 1280x1024 pixels)
Linux From Scratch 8.1
Bruce Dubbs has announced the release of Linux From Scratch (LFS) and Beyond Linux From Scratch (BLFS) 8.1. The new release of the book, which guides readers through building their own Linux distribution, offers many updated packages and several fixes over the previous 8.0 release of the Linux From Scratch instruction book. The release announcement states: "The Linux From Scratch community is pleased to announce the release of LFS version 8.1, LFS version 8.1 (systemd), BLFS version 8.1, and BLFS version 8.1 (systemd). This release is a major update to both LFS and BLFS. The LFS release includes updates to glibc-2.26, binutils-2.29, and gcc-7.2.0. In total, 32 packages were updated, fixes made to bootscripts, and changes to text have been made throughout the book. The BLFS version includes approximately 900 packages beyond the base Linux From Scratch Version 8.1 book. This release has over 885 updates from the previous version including numerous text and formatting changes." The guides are available in SysV init and systemd editions.
KaOS 2017.09
KaOS is an independently developed Linux distribution which focuses on providing a polished collection of KDE/Qt-based software. The project's latest snapshot, KaOS 2017.09, features a hardened Linux kernel with Address Space Layout Randomization (ASLR). The latest snapshot also includes the Nomad firewall utility and the Kooka scanner tool. "It has been a few years, but finally there is an up to date (Qt5/kf5 based) firewall application available again. Nomad-firewall is available on this ISO. A second scan application is added, Kooka (just ported to kf5). This application has quite a few more options than skanlite, so it is nice to be able to add a second (Qt/kf5 based) option for scanning. Krita 3.2 has the new option to use the G?MIC plugin. For that gmic-qt is added to the repositories. With this, the options to add effects to any artwork/image are sheer endless. A change in how printer packages are packaged makes it that now most printers are automatically recognized and setup, no need any longer to run any print wizard. This counts for both Live mode and installed system." Additional changes are detailed in the project's release announcement.
Manjaro Linux 17.0.3
Philip Müller has announced the release of an update to the Manjaro Linux distribution, a desktop-focused derivative of Arch Linux. This update, Manjaro Linux 17.0.3, brings a number of bug fixes and newer packages. It is also likely to be the last version of Manjaro Linux to support 32-bit computers. "Manjaro Gellivara was a great release! Now we are proud to announce v17.0.3, our final release of Gellivara. It took us a little over two months to finish this updated version. We improved our hardware detection, fixed some features in our installer (Calamares), added the latest packages available to our install media and polished our release as a whole. Everyone, who used older install media than v17.0.2 release, should read also this announcement about password weakness and follow its advice to secure your systems. Also, Gellivara is the last edition of Manjaro Linux supporting 32-bit Architecture. Read more about this decision here." The release announcement has more details.
IPFire 2.19 Core 113
IPfire is an independent Linux distribution for use on firewalls and routers. The project has released a new update, IPFire 2.19 Core Update 113. The new version includes the Who Is Online utility to assist administrators is viewing which network devices are connected. "This is the official release announcement for IPFire 2.19 – Core Update 113. The change log is rather short, but comes with a big new feature: Who Is Online? (or WIO in short) has finally arrived on IPFire. It has been ported by the original author Stephan Feddersen and Alex Marx and is available as a usual add-on package called wio. It is a built in monitoring service for the local network showing what devices are connected, which ones are on line and can also send alarms on various events. Give it a try!" Further details on this release and its updated packages can be found in the project's release announcement.
* * * * *
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: 553
- Total data uploaded: 15.3TB
|
| Upcoming Releases and Announcements |
|
Summary of expected upcoming releases
|
| Opinion Poll |
Is the package manager important?
There are many factors to consider when selecting a Linux distribution to install. People often look at the default desktop environment, whether a project is a rolling release or fixed, the range of package selection and default applications.
This week we would like to find out how big a roll the default package manager plays in your decision to install a distribution. Does it really matter to you whether a distro uses RPM, APT, Pacman or Emerge? Or is the package manager low level enough that you do not think about how software management works behind the scenes?
You can see the results of our previous poll on using Snap vs Flatpak in last week's edition. All previous poll results can be found in our poll archives.
|
Is the package manager important?
| Yes the package manager is very important to me: | 1058 (57%) |
| Yes the package manager is somewhat important to me: | 520 (28%) |
| No the package manager is not important to me: | 282 (15%) |
|
|
| DistroWatch.com News |
New projects added to database
BackSlash Linux
BackSlash Linux is an Ubuntu-based desktop distribution featuring a custom shell running on top of the KDE Plasma desktop. BackSlash features a user interface inspired by macOS.
BackSlash Linux Olaf -- Checking for updates
(full image size: 363kB, resolution: resolution: 1280x1024 pixels)
* * * * *
Distributions added to waiting list
- Namib GNU/Linux. Namib GNU/Linux is an Arch-based distribution featuring the MATE desktop environment. The graphical Calamares system installer assists users in setting up the operating system.
* * * * *
DistroWatch database summary
* * * * *
This concludes this week's issue of DistroWatch Weekly. The next instalment will be published on Monday, 11 September 2017. 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: 2, value: US$107.02) |
|
|
|
 bc1qxes3k2wq3uqzr074tkwwjmwfe63z70gwzfu4lx  lnurl1dp68gurn8ghj7ampd3kx2ar0veekzar0wd5xjtnrdakj7tnhv4kxctttdehhwm30d3h82unvwqhhxarpw3jkc7tzw4ex6cfexyfua2nr  86fA3qPTeQtNb2k1vLwEQaAp3XxkvvvXt69gSG5LGunXXikK9koPWZaRQgfFPBPWhMgXjPjccy9LA9xRFchPWQAnPvxh5Le paypal.me/distrowatchweekly • patreon.com/distrowatch |
|
| Extended Lifecycle Support by TuxCare |
|
|
| Reader Comments • Jump to last comment |
1 • Signal Private Messenger (by Elcaset on 2017-09-04 00:13:29 GMT from United States)
Comment deleted (off-topic).
2 • poll (by DaveW on 2017-09-04 00:29:14 GMT from United States)
My vote was that the package manager is not important. That is true in that it does not affect my choice for a distro. However, if it is not easy to use or does not work properly, then it becomes very important.
3 • Package manager (by Voncloft on 2017-09-04 01:00:36 GMT from United States)
The package manager is important to me: not the name or its method - but I have tried Linux From Scratch before and I flat out having to compile EVERYTHING! for every update of every package for every new feature - it is exhausting, I much prefer it be automated.
Rarely (while running Gentoo) will I compile from source manually.
4 • Is the package manager important???? Really! (by tom joad on 2017-09-04 01:22:08 GMT from Panama)
Holy Moly!!!
YES, the package manager is important. For me that is a make or break with an OS. The package manager can make or break an experience with a distro. Put another way, if one can not keep the system up to date in an efficient, effective way the system will struggle and the user will cut his losses and move on.
There is nothing worse than some cutesy, home brewed, ultra clever, esoteric and likely poorly documented package manager.
For me that is a resounding NO Thanks.
5 • Is the package manager important? (by JDNSW on 2017-09-04 01:32:09 GMT from Australia)
I answered "somewhat important". The reason for this is that explanatory text refers to the "default package manage". I use Mint KDE mostly (also Bodhi) and while I think the package manager is important, it is not necessarily the default one I use - I find synaptic much easier to use than Mint's package manager!
6 • package manager (by bhrich902 on 2017-09-04 01:36:01 GMT from United States)
I think the question should of focused on graphical package manager. I personally could care less if the end of the package is a .rpm, .deb etc.... All the command line tools will, at the very least, install/remove, update and resolve dependencies.
However, a graphical package manager that does those basic things along with a graphical update manager is very important to me when choosing a distro to play with.
7 • Package manager (by OhioJoe on 2017-09-04 01:39:58 GMT from United States)
I am not a command line kind of guy, so I prefer a graphical package manager.
Synaptic is fine. Void had OctoXBPS, but I am not sure it is still available.
8 • What is inside the package? (by Fired Manager on 2017-09-04 01:46:14 GMT from Canada)
Does anyone ever care to open a package for a inside look whats in there, with a manager already fired?
9 • package manager (by kleshas on 2017-09-04 01:49:37 GMT from Canada)
I only use arch for daily use.
For cert. studying, I have other OS's and the package manager is irrelevant.
10 • Package manager (by Bobbie Sellers on 2017-09-04 01:50:42 GMT from United States)
Of course the package manager is important when running a rolling release
as I do, PCLinuxOS64. There about half a dozen packages I add to any
release in order to have my tools handy. In addition in PCLinux we have
lately frequent kernel updates which the excellent package manager
Synaptic lets me install to try out without hassle. Presently have 4.12.10
working like a charm on both the community pclinuxOS64 kde and
Tde(Trinity Desktop Environmen) as well as here on the HP Pavilion
with the KDE Plasma 5 version.
.
11 • Package manager importance (by Doug M on 2017-09-04 02:05:13 GMT from United States)
I voted somewhat important as I didn't feel the other 2 options fit.
Which Package manager is unimportant, as long as it does the job that it is supposed to do.
If it can't do the job, that distro gets wiped quickly as I am not enough of a Linux guru to keep a system up to date without a package manager that resolves dependencies.
12 • peeking into packages (by tim on 2017-09-04 03:50:16 GMT from United States)
@8 yes, I often peek at package contents or, for uninstalled packages, package manifests.
I was asked recently: "Does the debian 'font-manager' package actually install any additional fonts?" and was able to browse
https://packages.debian.org/stretch/amd64/font-manager/filelist
to find the answer (no, that package does not install any additional fontsets)
Similarly, a recently-read question led me to go check "The firefox-esr from Debian still supports alsa, right?"
https://sources.debian.net/src/firefox-esr/52.3.0esr-2/debian/browser.mozconfig.in/
(yes, the configuration in Debian's firefox-esr 52.3.0 package does specify --enable-alsa )
On a Debian system, you can view per-package "list of installed files" via (dpkg-query at commandline or) via the Synaptic package manager GUI. I usually choose the latter.
After downloading a *.deb package from a non-debian (github, sourceforge) repository, I nearly always use the gdebi utility to inspect the package contents. Doing so avoids running into "gotchas", a frequent one seems to be ubuntu-specific install destination paths.
Supplemental to what Jessie covered in Tips-n-Tricks, Void Linux provides an interfaces to search/browse their packages.
https://www.voidlinux.eu/packages/
We can, for instance search firefox-esr, and clickthru to
https://github.com/voidlinux/void-packages/blob/master/srcpkgs/firefox-esr/files/mozconfig
and read that their current firefox-esr is v52.2.0 (and the config doesn't mention alsa). Does Void patch their build to change mozilla's specified default --enable-pulseaudio? From what I can see, they do not:
https://github.com/voidlinux/void-packages/tree/master/srcpkgs/firefox-esr/patches
13 • ext4 apparently evaporated! (by OS2_user on 2017-09-04 04:10:48 GMT from United States)
First: I'm only describing trying to USE Linux this week.
Had a drive problem to fsck, so went into Terminal first time on PCLinux 2017.04 install and got sidetracked immediately: I CANNOT READ BLUE OR RED TEXT EVEN IN LARGE FONT, though have normal color perception, so LS output of directories in blue and the red prompt are NEARLY USELESS, and with the GREEN text it's just cartoonish! -- I want PLAIN white on black text, ALL the text, ALL the time. I'll figure out which is what soon as I can READ it. Normal folk gave up on multi-color text in the 90s after brief novelty. Even Microsoft has readable command line by default. EVEN MICROSOFT. (I see in Jesse's review above: "There are some other odd design choices too. For example the virtual terminal application has a bright blue background. The default fonts tend to have a tall, thin look which I found hard on my eyes after a while.")
First must name a "profile", but that's only learned after selected color scheme and hit "OK". Then I can embiggen the font: that worked. Resume trying to figure out why the text color doesn't actually change as seen to sides: OH, the "scheme" changes only what you type, rest still infuriating blue and red with no obvious way to change. I try the color picker, but can't figure it out, and the dialog box dies; its "OK" and "Apply" and even "Cancel" buttons just don't work, can only get rid of by Close. It leaves part in the prior dialogue, must re-open. -- Every time tried. -- Give up in disgust: if picking colors is THAT difficult, I'll just do so little as possible in Linux!
On to SECOND GOTCHA. Tiny green text again in new terminal window even after thought had properly entered a named profile. Nope. Though a field on one tab accepted it, actually you must FIRST go into "Manage Profiles" to enter name, THEN can select profile, THEN set colors and font size. And yet later go back and set it as default.
About then, recalled why CRINGE every time think of going to Linux command line. Can't have even text PLAIN the way I like without long trial-and-error learning how to UNDO needless obstacles.
By luck, forgot and typed "dir" as in MS-DOS, got directories in white text! Hooray! Now only prompt is stupid red. Lucky again when "fsck" caused mention of fsck.ext4 which has decent help built-in.
After 15 minutes wasted, back to the drive problem: first, figure out what the hell to specify! Each drive has least four possible names: here "sbd" in partitioning, that and "sdb1" in \dev, "primary" automatically appeared in KDE; and long string of alphas and numbers in the message that it was gone! -- SHEESH! -- NO, guys, it is NOT reasonable once "learned". Partition naming is not only arbitrary, it's MULTIPLE, and highly confusing. To keep simplest I make only one partition per drive, and would like same / similar name: point here is Linux has defaults I don't know how to change, and error messages of apparently random numbers and letters STILL wouldn't be easily related to drive. Lucky have only two drives and of differing size!
HERE'S A SHOCK! -- Problem appears not the 2-month-old WD 3T drive, but that ext4 file system simply rotted! Most subdirectories became empty, and a bit later BOTH superblocks faded too! KDE removed it from list. Fsck could do nothing! -- Reboot got it to appear again in KDE list. Formatted normally, then testing works, but so did prior 2T of data last for a while...
Oh, well! Only a FEW hours to copy a couple terabytes from OS/2 over 100Mbit FTP! -- Now, I've used FTP to Linux for backups since 2007, and it HAS BEEN reliable through three or four systems (with random used drives!), but now I'm not sure: this looks like progressive failure of ext4, not the NEW drive. -- I should get a gigabit switch expecting the latest ext4 to fall apart often? But big gain here: learned more Linux, how to use fsck.ext4!
Guys, your too-complex software built on creaky 1960's design is truly becoming UNUSABLE. -- And I admit that my IQ drops from barely adequate to single-digits when INFURIATED by cartoonish color text but that's because it's WORSE than 1960's monochrome!
Anyway... Yes, thank you, it's worth every cent I paid, and I DO know where to stick my advice. That won't fix the problems with Linux, though.
14 • Nitrux (by Andy Prough on 2017-09-04 04:38:31 GMT from United States)
Got to wonder how many distros in the database are totally non-functional messes like this one? Good job trying to review it Jessie, and good job getting it to work even in a VM. This is why Distrowatch's user ratings are so important.
15 • @13 - OS2 user (by Tony on 2017-09-04 04:58:05 GMT from Thailand)
Firstly: PCLinuxOS is at version 2017.07
Don't use old versions
Secondly : I am a 72 year old fart with an average IQ and I certainly am not an expert.
I use PCLinuxOS without trouble and without any of the problems you describe.
Thirdly: If you have problems, don't put them on Distrowatch.Go to the pclinuxos forums. There are dozens of people to help you
16 • Nitrux and Ext4 (by RJA on 2017-09-04 05:08:20 GMT from United States)
The Nitrux review was mixed, can't believe it's failing on a desktop. @Jesse, did you see a kernel panic? And if you did, was it this or similar?:
kernel panic-not syncing: VFS: unable to mount root fs on unknown block x,y
Some Linux kernels for some reason seem to hate some ATA controllers for no very obvious reason! I know that it seems that the mainstream/mainline? kernel, if not all in the past, hated the ATA controller on a Dell Dimension 2350 and/or at least on a couple of socket 775 motherboards made for Dell made by Foxconn, the Vostro 200 and Inspiron 530s and would give a kernel panic like that.
17 • Package manager: why it matters to me (by Brenton Horne on 2017-09-04 07:10:55 GMT from Australia)
I favour distributions that have two major package management features:
(1) VERY extensive repositories, especially their official repositories, including all, or at least most, of my favourite software (which includes some proprietary software like RuneScape's NXT Client)
(2) Ease of creating one's own packages (in case the software I want is not in the repos of the distro already) and bumping the package version for existing packages in the repositories in case the maintainer gets a little slack/busy/lazy/other.
(1) is satisfied best by Arch Linux (and its derivatives) and, to a lesser extent, Gentoo Linux. (2) is best satisfied by Arch Linux and to a lesser extent Gentoo Linux and RPM-based distros like Fedora and openSUSE.
18 • Package manager (by Kazlu on 2017-09-04 09:38:30 GMT from France)
Apparently different people understood the poll differently this week... I answered according to my comprehension, being: "is the low-level command line default package manager (apt-get, pacman, urpmi...) installed on your distribution important?"
I answered no since I couldn't care less about the default package manager used in my distro... as long as it's there. Similarly to #11 I also need it to resolve dependancies, but if the low-level package manager does not resolve dependancies and there is a graphical front-end that does it instead, that's fine (I don't know any example of such a configuration). So in my opinion, what package manager itself is not important but the OS must be able to manage dependancies in order to ease software installation.
19 • @13, Linux ease of use (by jg on 2017-09-04 09:47:18 GMT from Poland)
@13 I use Linux (WEB browsing, movies) since 2001 and I am not a developer/programmer and I can give you this advice free (I hope it's worth more than what it was paid for) - if and when doing something that is new to you or you do it first time - in Linux - it pays extremely well to first research the subject on Google or relevant forums. Most often reading 1-2 items that appear on Google results page would be enough. Even today, every now and then, when undoing that mess I created I say to myself - why didn't I ask a stupid question on Google first?
Without doing that, you just get what you paid for - nothing.
I had similar problems with Gnome terminal, but I must say I quicly deciphered the Profile/Session riddle and changed the terminal looks the way I wanted.
As to 3TB drives, this really should prompt you to do a little research - GPT, ext4, etc.
If you don't like pclinuxos, (another free advice) try Ubuntu Mate - the latest 17.10 beta 1 is pretty stable, fully functional out of the box and practical for a home user. I used to run Xubuntu (XFCE) but unfortunately it really starts showing its age.
20 • @13 Coloured text (by Charles on 2017-09-04 10:31:17 GMT from United Kingdom)
"By luck, forgot and typed "dir" as in MS-DOS, got directories in white text!"
I know this won't change your opinions on Linux but in the interests of trying to help, I strongly suspect that in your ~/.bashrc file you have this line: alias ls='ls --color=auto'
Comment it out/remove it and then when you 'ls' you won't have coloured text.
21 • Package Manager (by jymm on 2017-09-04 10:51:24 GMT from United States)
Yes the package manager is important to me. I will only use distributions that have APT and Synaptic. Probably because my first OS was Debian based. I am familiar with that package manager and have no great desire to learn another list of commands. I also love Synaptic, which lets me look for packages I might not otherwise be aware of their existence or use.
22 • PCLinuxOS/package managers (by Dave Postles on 2017-09-04 11:24:46 GMT from United Kingdom)
@13 My default console in PCLinuxOS has white for user and red prompt for root. That's it.
Package managers. I have no issue with using urpmi, dnf, or apt-get, but I do NOT like emerge.
23 • The question for Package Manager perhaps is built wrong ... (by Gerhard Goetzhaber on 2017-09-04 12:22:27 GMT from Austria)
... for it should better sound like this: "What package format do you prefer, respectively NEED?"
As of these days, on many a Linux distro you can work a lot, and results will be fine - if you're satisfied by screen output as well as by input through keyboard and mouse or touch-screen! In a lot of cases, however, you want to connect AND OPERATE things like a printer, a scanner or (if using a desktop station) an uninterbreakable power supply. All such peripherials for most require a driver. The joke is: Today more and more manufacturers do deliver Linux drivers, but their packages are either .rpm or .deb, and the sources combined with such support are quite specialized to make same type packages.
On the other side, distro families like Arch, Slackware, Gentoo, LFS or even more exotic systems cynicly spare any useful documentation of their inner system architecture and of package (and within dependency) name conventions! When you then try to modify a driver to get used with any of those systems you will heavily fail unless you are a professional systems' analyzer.
Me, I have a Canon Colour Laser Jet which requires Canon's UFR2LT driver enhancement for CUPS (big problems there even on Ubuntu and Debian with recent CUPS versions!), an Epson Perfection V370 Photo scanner also depending on some proprietary software, and an UPS from the British manufacturer Eaton communicating with the dsektop or server by IPP software only.
The conclusion is: Whenever tempting work on Linux together with peripheral hardware anyhow challenging you cannot do but staying with Debian, Ubuntu, RedHat/Fedora, OpenSUSE or their derivates ...
24 • Nitrux, Package Manager (by dragonmouth on 2017-09-04 12:54:17 GMT from United States)
Nitrux & BackSlash:
Why do we need another Ubuntu-based dsitro with KDE desktop if we already have Kubuntu?! What is the advantage of Nitrux or BackSlash over Kubuntu? A different look and feel? Nitrux and BackSlash are a perfect example of proliferation of unneeded distros. What Nitrux attempts to bring to the table can be handled by installing some packages from Kubuntu repositories or from PPAs. The macOS look can be added to Kubuntu by installing an appropriate theme. There is no need for an entire new distros just to do this. I know that one of the basic tenets of Linux is 'choice' but to crank out a distro just because one most often results in something barely usable like Nitrux. How many of the 570 dormant and discontinued distros in the DW database are similar in quality and utility to Nitrux?
Package Manager:
Whether a distro uses RPM, APT, Pacman or Emerge as a command line package manager is not important in my choice of a distro. The CLI products always work. When it comes to GUI package managers, I have yet to find a more useful and functional one than Synaptic. It may be old and it may not have a 'modern' look but it does not try to replace functionality with glitz and eye-candy.
25 • @13 OS2_User: (by dragonmouth on 2017-09-04 13:02:51 GMT from United States)
Did you ever hear of 'Settings' to change the look of your Desktop and Terminal?
I also use PCLOS and my console background is light green with black test. My Terminal background is sunshine yellow with black text. Instead of complaining how bad Linux in general and PCLinuxOS in particular is, experiment with your Settings and/or Themes.
26 • Package managers (by Bonky Ozmond on 2017-09-04 13:12:56 GMT from Nicaragua)
I use Gentoo / slackware or derivatives generally And quite like Emerge though spent most of my 11 yrs compiling an having more control of what i get...
I have no issues with Pacman which is quite good....
I like Voids offering.
Never been a Big fan of the GUI based things much prefer any CLI types...
I do wish we had more developers making apps / programs for linux it seems we are all using the same things on every distro these days
27 • Package Manager (by Stan on 2017-09-04 13:15:53 GMT from Netherlands)
Are we serioysly going to discuss this?
Update your entire system from 1 line of code vs manually updating user land software or manage 10+ individual update manages?
28 • Package managers... (by OstroL on 2017-09-04 13:57:51 GMT from Poland)
Package managers are good, if they do what they are supposed to do, and they usually do that. As we are always on the "development," sometimes a package manager could trouble you by uninstalling a very good working app, just because it is old or some of the needed dependencies for that app. So, to keep such apps from getting damaged by the package manager trying to update the whole system, you have to make the package manager blind to that app(s).
So, the need of self-contained apps, such as AppImages, Flatpaks and Snaps. This way you need to update only your system, not the apps. You can also use an old app without the worry that the 'package manager' trying to do you a favour by uninstalling it.
29 • Is the package manager important? Of course (by Andre on 2017-09-04 14:21:27 GMT from Canada)
I'm with @4 on this one. The package manager is a make-it-or-break-it thing.
I have some very specific requirements of my package manager, and find a lot of the ones currently available across the Linux landscape rather unsatisfactory. In fact, one of the biggest reasons I don't use Debian-based distros is because I find APT and friends quite limited in what they allow you to do. And no, an assortment of GUI front-ends is not the answer.
Package management is nowhere near where it should be on most platforms. The only people who will tell you otherwise are the ones who do nothing else but use the upgrade option.
30 • Package manager's role (by Jordan on 2017-09-04 14:46:07 GMT from United States)
"...how big a roll...?" Bear claws are nice big rolls. ;)
How big of a role? ;).
31 • @12 peeking into packages (by Hendryk on 2017-09-04 15:38:18 GMT from Germany)
Void linux builds firefox-esr with alsa support.check the firefox-esr template: https://github.com/voidlinux/void-packages/blob/master/srcpkgs/firefox-esr/template
Also a note to jessie, regarding the xbps-src discussion (which was a nice one to see here, thanks):
./xbps-src is the command to run the framework inside the void-packages folder (which is by the way the only script to work with in there, so all other commands would _not_ need ./ prefixed)
./xbps-src install does in fact not install pacakge in your system but inside the build enviroenment as the "install" subcommand is the explicit call of the named build phase (under the circumstance it has been compiled via subcommand "build" before, as well as all other phases have been run too).
For actual installation of a manually built package, the call of "xi " inside the void-packages folder does the job, as "xi" is a wrapper for "xbps-install " which takes the xbps-src reporitoy into account automatically. plain "xbps-install " would not.
(see man xtools for more).
Cheers and have a nice week
32 • Mint’s “new” progress bar feature (by SuperOscar on 2017-09-04 16:02:45 GMT from Finland)
From the news:
”The Linux Mint team has unveiled a few new changes that will be coming to the distribution in the near future. One feature grants applications the ability to share progress information with the desktop environment, which allows a progress bar to be displayed in the task switcher.”
Isn’t that what KDE Plasma already does and has done at least since version 4 point something?
33 • Package Manager Poll (by cykodrone on 2017-09-04 16:43:22 GMT from Canada)
I'm no n00b but I'm no server room maintainer either (I wish I was, I'd set up a cot in their, lol), that being said I've tested, poked, prodded, crashed on purpose, performed autopsies on and researched many distros to death over the years, I had to give every base flavour (Slack, Gentoo, Debian, Red Hat, etc) a chance. PMs that build apps from source, while really cool and a great idea, don't always work and can take a long time, if it cries for a dependency, you'll be stuck in the PM even longer. Binary package managers (rpm and deb being among the oldest and most popular) took on the dependency issues, which is all good if you don't mind aging and stale apps. In my experience, it boiled down to a battle between rpms and debs, the distro didn't matter, as long as it had a decent GUI and it worked. The final most important issues to me were the amount of available packages, package reliability, available backports/3rd party repos, and functionality of the package manager itself (in and out of a GUI, I'm GUI spoiled). Debian (apt) based distros solved most of those problems and have been the most reliable, but I'm a desktop guy running GUI distros on self-built PCs, everybody has their own needs and wants. I went from Mepis to Ubuntu based (pre spyware and bloat) to Debian (pre-systemd) to Devuan. I keep PCLinuxOS on another drive solely because of FF Multi Converter, and even PCLinuxOS deals with its rpms with apt (Synaptic).
While I've never tried Nitrux, I highly doubt it will be snappy on a 5 1/2 year old low end budget processor. It's Ubuntu based (complete with kernel/system suffocating systemd) with a Plasma based GUI, I dumped KDE/Plasma years ago because of bloat and functionality issues. Xfce seems to be the only old school GUI left on survivor island that's reliable and compatible with most apps and processes.
34 • Your Future Is Void (by Arch Watcher 402563 on 2017-09-04 17:44:03 GMT from United States)
The key thing for a package manager is checking package sigs for security. After that, dependency management. After that, speed/interface/etc.
Void's hybrid binary/source approach is nearly unique in Linux distros, although I gather a few Gentooish ones now go that way, and NixOS after a fashion.
The following in-depth reviewer thinks very highly of Void. He says it's the future of Linux. What makes him worth hearing is age and experience. He's a dinosaur and used all major distros.
https://www.youtube.com/watch?v=fzkl2xcqQOI
35 • Package manager (by Jyrki on 2017-09-04 20:26:12 GMT from Czech Republic)
package manager is not important at all, as long as it's pacman. For me package manager is one of the decision maker for go or not go with the distro.
I hate all the gui frontends to package managers, this is the very first thing I turn off and uninstall.
36 • Package Manager = OS (by david esktorp on 2017-09-04 21:40:03 GMT from United States)
The package manager (or lack thereof) is The Prime Distinguishing Feature of all Linux distributions. When you look at the differences between the mainline 'independant' distributions, the key difference is always package management. Change the package manager and it's a different OS. Whether the end user notices the differences is another story.
37 • Manjaro dropping 32-bit support/Is the package manager important? (by A-holeLinux on 2017-09-04 22:01:50 GMT from Netherlands)
Sometimes I think…..Who Is actually selecting and asking the Questions on Distrowatch ?
Is it a Kid? Is it some one very very Educated? Or is it Artificial?
And we all answer so nicely….
Manjaro dropping 32-bit support. No problem, that is good. Never have used Manjaros 32bit Phenomena.
Pacman or Emerge? I do not know..You narrowing down, for what?
Greetings to all
Thank you DistroW.
38 • #36 (by Microlinux on 2017-09-04 22:22:56 GMT from France)
Here's at least ten differences between Linux distributions: 1. package manager 2. quality of documentation 3. release cycle 4. support cycle 5. stable vs. rolling release 6. low-risk updates for enterprise use 7. installer 8. default software selection 9. available software in repos 10. free as in {speech,beer}?
Cheers.
39 • Package Managers (by edked on 2017-09-04 22:41:43 GMT from Canada)
While I'm usually fairly easygoing about package managers (I've only really interacted with apt-based distros and pacman-using arch-based ones), and move fairly easily between GUI and command line (I find CL more reliable and oddly less hassle for system upgrades & updates, but appreciate a GUI for browsing and individual application installs), if there's one thing that makes me wary of a distro, it's a review (here or wherever) with a line like "Prawn Linux uses its own unique custom-written package manager, PoopyButt, which has a number of idiosyncrasies and unusual defaults."
I usually hit the brakes on my interest pretty hard when I see something like that.
40 • @39, etc. (by claudecat on 2017-09-05 01:06:31 GMT from United States)
"...if there's one thing that makes me wary of a distro, it's a review (here or wherever) with a line like "Prawn Linux uses its own unique custom-written package manager..."
See, that makes me more interested, not less. I most respect and enjoy using distributions that do things in original ways, and package management is one of the few areas left where there's room for something new.
Sure, it may be reinventing the wheel to some degree, but I'd rather see original approaches to packaging and the management thereof than yet more glossed-up 'buntu/Debian progeny working with the same infrastructure of packages.
Examples of such original distributions would be Void (excellent yet at times cryptically documented), Gentoo (and other Portage-based entities), Solus, Pardus (back when it was a thing and maybe again with Pisi), Slackware of course, and others with which I'm less familiar.
The oddball distro to me is PCLOS, which uses apt/Synaptic with RPMs, and very smoothly. I've always wondered why more distros haven't used this approach. Everything else gets borrowed/stolen/shared...
All that aside, my favorite package managers would probably be pacman (speed, elegance) and Gentoo's emerge/Portage, which I hope one day to fully understand.
Least favorite? Anyone remember Foresight Linux and conary? Maybe a great idea, but it didn't work (out) so well.
41 • Package Managers / PClinuxOS (by Winchester on 2017-09-05 02:43:13 GMT from United States)
As far as the old Foresight Linux and its package management goes,it gets much worse than that.
Open Mamba package management was not all that great. Stella,which is based on RedHat 6.8 with Gnome 2,has a graphical package manager which looks similar to Synaptic but is crippled in comparison. The search function is horrible. Otherwise that distribution runs very well on some old,limited hardware (Asus EeePC).
Package management is one of the very few drawbacks of the Puppy distributions. Trying to go from FireFox 52.2 ESR to 52.3 ESR in LxPupSC,I ended up with both versions of the browser,the newer one without any modifications to the default settings carried over. Otherwise,a great distribution.
PClinuxOS is a fine operating system. Synaptic in PClinuxOS offers the option to "Verify Package Signatures". In my installation from the Trinity Big Daddy community iso,I have to log into the root account in order to launch Synaptic. You can also use apt-get to install updates via the "Update Notification Applet" (as a normal user) which launches the XTerm and prompts for a password. There is also "KPackage" which I haven't really experimented with so far.
Regarding post # 13,apparently not a KDE Plasma person,at least not in PClinuxOS,so I would recommend trying PClinuxOS with another environment such as the aforementioned Trinity "Big Daddy" edition or the LXDE community edition,or maybe just install a window manager. Using the ext3 file system and something other than a Western Digital hard drive which can be hit or miss depending on the model. I would go with HGST (owned by Western Digital but generally better than most Western Digital branded drives) for a mechanical drive. HGST can be thought of as a higher-end Western Digital. For a solid state drive, Crucial or maybe Intel seem to be the best.
My Xterm,by default,has an off-white background with black text. My Konsole terminal,by default,has a white background with black text. In Konsole,you can just go to the "settings" tab and then "Schema" in the drop down,then choose from 18 different color schemes although some of them appear to be the same or very similar and I have not yet figured out how to save a scheme as the default other than the original default. I haven't looked into it yet but,I imagine that I would just have to copy the scheme into my home folder and edit the konsolerc file in /.trinity/share/config/ .
Regarding post # 17,if you want very extensive repositories,PClinuxOS is a solid option in that regard as well.
Regarding post # 16, kernel 3.16 (Debian Packaged) and kernel 3.13.125 (on SalentOS 14.04 64-bit) both work without panic on a Dell Inspiron 530s.
42 • @40 (by edked on 2017-09-05 02:54:58 GMT from Canada)
Oh, Gentoo and Slackware are definitely not like the others, being "mother distros" that have been around almost as long as linux itself, so their package managers don't evoke the same wariness, due to their venerability.
I'm more talking about newly-popped-up operations, especially where the homebrewed PM is created for a distro based on a family that already has plenty.
Oh, and I'm well out of Debian/'buntu apt-land, having moved happily to planet pacman.
If I want to try a new package manager, I'll move over to an rpm distro, or actually try Gentoo or slackware, rather than fiddle with an experimental PM while going back to apt-land.
43 • Packaging in the Distant Past (by Peter Besenbruch on 2017-09-05 06:26:45 GMT from United States)
When I sought to try Linux starting back in 2002, I read books. They explained that there were two kinds of distributions, DEB distros and RPM distros. RPM distros put you through something called "dependency hell." DEB distros fixed all that. I tried a variety from both camps, encountered dependency hell, and stuck with DEBs from then on. Eventually, as I got better, and Debian got easier, I moved to Debian itself.
Nowadays, lots of package managers do their job well, but "apt-get" has a special place in my heart. It has successfully gotten me through countless major upgrades, to say nothing of the minor stuff.
44 • Package Managers (by Alessandro di Roma on 2017-09-05 08:22:33 GMT from Italy)
But what do you mean with "package manager"? The package system (DEB, RPM...) or the package management tool? In the first case my answer is "very important", in the second one is "somewhat important".
I use Xubuntu, which as a Debian-derivate has DEB package system, but has not preinstalled synaptic, my preferred package management tool. Of course is not a problem to type "sudo apt -y install synaptic". In fact I use both "sudo apt" on terminal and synaptic.
In order to keep the system up-to-date I wrote a one-line script (named "upgrade") containing:
sudo apt -y update && sudo apt -y upgrade && sudo apt -y autoremove
45 • Pacman and Apt (by Guido on 2017-09-05 08:51:56 GMT from Philippines)
I have used Manjaro 32 bit for some time. It has Pacman. I got used to it. Now they decided to drop the support for 32 bit machines, cos they are based on Arch Linux, which drops also.
Now I am back on Ubuntu with Apt.
Beside the commands are different, it is not so important, what package system you are using, as long as they are really working! Pacman is faster, Apt maybe smaller... Both systems are excellent.
For both are managers available with small differences. In other words, all packages are good, as long as they are working and being up-to-date.
46 • 32-bit (by Winchester on 2017-09-05 14:40:39 GMT from United States)
Correct me if I am wrong but,didn't Debian and Ubuntu both announce plans to phase out 32-bit support over the course of the next few years?? I know that they still support it right now but,I don't think that they plan to continue moving ahead into the future.
The same goes for ArchBox. You can install ArchBox 32-bit right now but,being based on Arch Linux,obviously,32-bit seems doomed with that distribution as well.
That would leave the Gentoo family,the Slackware family,the Puppy Linux family (those using Slackware Packages) ,SliTaz,and TinyCore / CorePlus as options for 32-bit machines. Maybe a couple of others but,not many.
47 • @38 (by david esktorp on 2017-09-05 18:19:05 GMT from United States)
That's why I said "The Prime Distinguishing Feature" and not "The Only Difference" ;)
48 • Phasing out 32-bit (by david esktorp on 2017-09-05 18:28:06 GMT from United States)
Something else to consider regarding 32-bit and/or 'legacy' systems is the possibility of simply sticking with outdated yet stable operating systems. For example, if a system is not used for any important financial tasks, security, etc.. there is virtually no reason to need an 'up-to-date' system. Security updates are way overhyped in many situations.
If a user decided to install Ubuntu 10.04 and disable all updates, there is still almost zero chance of getting 'hacked' or being victimized from some corner-case security vulnerabilities.
Overblown 'bleeding edge' security update hysterics is one of the Linux communities biggest problems.
49 • Main Differences Between Distros (it's all about perspective) (by M.Z. on 2017-09-05 20:35:47 GMT from United States)
@47 & @38
I think the big things that make a difference for desktop users are 1) the Desktop Environment & 2) the tools used to admin the OS. The first point is obvious on the level of day to day interaction, & the second makes a huge difference in over the course of using the distro. For instance, there are big differences between Mint Tools that come in a variety of forms (independently created software manager, repo manager etc.) & the centralized Mageia/PCLinuxOS control center. From where I sit each individual Mint Tool feels designed to be friendlier to average desktop users, while the Mageia/PCLOS Control Center offers something more cohesive, but also a bit more technical. One prime example would be the installing software from Mint Software Center vs launching drakrpm in MCC (or Synaptic in PCLOS). In the control center case you get a fairly simplistic text based GUI package manager, but you can switch to doing updates or most any other admin task without a second password, where Mint feels friendlier for the single task of installing software with a more GUI oriented UI that includes more pictures & user reviews; however, you'll end up entering your password more to do other admin tasks.
Anyway, the DE & admin tools are fairly important for most users, while the back end stuff can feel very interchangeable. For instance in the case of PCLOS & Mint, both can use Synaptic even though there are significant differences going on underneath the hood with Deb or RPM packages. For some users that like Synaptic this could make the two nearly equivalent from a package management perspective, but then there are a lot of other factors that could could be important to other users. I could care less about my init & go back & forth between Mageia & PCLinuxOS on different PCs fairly often, but some people may avoid one or the other due to systemd. The init thing seems fairly silly to me, but it's a matter of perspective, much like focusing on 'Only Libre Software', or having 50k software packages vs having the few packages I really need & the DE I want by default.
Given that there are millions of Linux users & a large number of major projects creating distros, you are going to end up with a fairly large set of things that are important way to differentiate for some users & not important to others. It all depends on what you are looking for & what is important to you when looking for a distro.
50 • Not concerned about package managers? (by Silent Warrior on 2017-09-06 03:48:30 GMT from Sweden)
I voted 'Nope'. Now excuse me while I download a Nitrux image for testing in VirtualBox for the experience of using .deb packages with pacman. Because I'm so very consistent. :-)
51 • Dropping 32-bit (by FOSSilizing Dinosaur on 2017-09-06 12:31:27 GMT from United States)
From what I've seen,downloads of new ISOs 64-vs-32 run 2:1. That suggests interest, at least.
One reason for using 32-bit is performance; one reason for dropping it is reducing (duplication in?) development overhead and workload.
52 • CLI vs package manager (by frenly on 2017-09-07 00:30:36 GMT from Australia)
There are thousands of linux apps out there. but when you search for uncommon apps in a package manager like synaptic you can never find them. It only shows the most common apps.You need to "add repositories" for more apps. Where are these repositories? Why aren't they already added?
In Susestudio you can make your own distro. But you can't find those uncommon apps listed there either - even after adding all their repositories. Apparently you need to add even more (external) repositories or import the apps directly.
But there are no such problems when you use something like APT on the CLI. Just search for the app name, download it, and it is installed automatically. So official package managers seem unnecessarily restricted by the need to add obscure repositories.
53 • @52 (by Black Knight on 2017-09-07 02:31:30 GMT from France)
Maybe I don't understand well your post but this is wrong.
Apt seeks the apps in the repos which are on your system, exactly as Synaptic and other packages managers. You must have the repos also for Apt. Both works in the same manner. If you have not the app that you want in the repos on your system, it does not matter if you seek it with Apt or with the packages manager, you won't find it.
54 • Searching for apps (by Kragle von Schnitzelbank on 2017-09-07 02:37:04 GMT from United States)
@52 • @53 ... and some apps aren't in any repository. Uncommon, like 'e said.
55 • package kruft (by frenly on 2017-09-07 04:30:21 GMT from Australia)
@53 Well, GUI package managers list not only apps but also dependencies: libraries, addons, extensions etc. With the CLI you just need to know the app name. Or, you can get a portable app via flatpak/snap/appimage,
And trying to build a distro with Susestudio or Slax online builders is difficult because of all the dependency listings that you need to wade through to find what you want.
56 • 32 bit and PowerPC (by Knut Stormfoss on 2017-09-07 07:43:04 GMT from Norway)
PowerPC ports (32 bit PowerPC) were phased out from most distros a few years ago, but a few still had support until last year. This started with Ubuntu around 12.10 and trickled down to the other distros over time. Most distros never supported PowerPC at all, so the only real options were Debian-based. Ubuntu spins like Lubuntu and Ubuntu MATE supported PowerPC until 16.04 LTS whiich means there are a few more years of life in these machines. I think Lubuntu only has three years of support on the LTS, while Ubuntu MATE might have the full five years. Users of PowerPC Macs from 2005 have pretty underpowered hardware by now, so it is not unreasonable for distros to phase out support to avoid some extra work when only a few enthusiasts really use these machines any more. The PowerPC Luddite and similar blogs are still out there, but the activity is really low by now.
32 bit x86 has generally not been used on real hardware since the end of the netbook craze around 2010. Almost all distros have had support for this architecture until Arch dropped support last year. Ubuntu and Debian dropping support seems somewhat early, but on the other hand, Ubuntu 16.04 LTS and all the respins will be supported until 2021, and many other distros specifically for lower end hardware will probably support 32 bit x86 at least until then.
By that time, netbooks and lower powered laptops with 32 bit x86 processor will be pretty underpowered. (More so than the high-end G4s and G5s Apple shipped in 2006 are today. These go up to quad core 2,5 GHz G5s with 16 GB RAM and high-end graphics cards.) It is not unreasonable for distros to start thinking about dropping support when it involves extra work and critical bugs can hold releases back. And if Cannonical start thinking about it now, they still have to support 32 bit x86 until 2021. Debian is slightly more surprising, since they have generally kept support longer and since they do not have LTSes, the newest Stable release have to have support for people to be able to use their distro at all.
Generally, the fewer ports a distro has, the faster new releases can come out and the more focus can be used on polishing things up instead of fixing bugs for architectures few people use. It is good for AMD64 to have some competition from other architectures, but to have two different x86 architectures from the same manufacturers isn't competition. ARM is getting more important every day, but it is a pity that there isn't one instruction set, but more, and that distros need to make ports for each of them if they want to support ARM hardware well. It would be really good if there were four or five competing processor architectures around, but that within each architecture, there would be only one instruction set and hence only need for one port of each distro.
In reality, most distros will never go beyond x86, but for those that do aim at being more universal (like Debian), people cannot demand a port for their architecture without also contributing time and/or money. The reason why Debian had to drop PowerPC support after Jessie is that there were too few porters and testers on the platform to make it viable. If people want 32 bit X86, then they need to step up and do the work.
57 • Package Mgr (by argent on 2017-09-08 04:56:37 GMT from United States)
Yes, a package manager is quite important to me! Good way for me to look at a new application quickly, such as size, dependencies, etc would be by Synaptic. Helps me keep KDE, Qt or any undesirable dependencies off my install.
Synaptic also allows a viewer to see other packages they may want to install. Searching with Synaptic can either be by name or by description along with other search possibilities.
Have used Octopi and Pacman depending on the DE/Wm and distribution.
Package management is very important and with a GUI so that those who aren't yet quite savvy on installing from source, or even knowing just exactly what they need is important.
58 • BackSlash Linux (by Sanjay Prasad (Kolkata) on 2017-09-08 10:23:16 GMT from India)
BackSlash Linux looking awesome, I am not a fan of MAC but customized shell that runs on the KDE Plasma desktop 5.9.x is great, going to download 1.7GB iso ....
59 • Post # 48 (by Winchester on 2017-09-08 11:53:09 GMT from United States)
That's a new take. I have never heard any advocate for the usage of old and unmaintained distributions.
My e-mail is crippled in old web browsers,even FireFox 45.9 ESR. For it to work properly,I need to use at least 49 or 52.x ESR.
It just doesn't seem like the best idea to use an unmaintained distribution unless there are no other options for the given hardware. And there are other options for 32-bit hardware. I could see having one on a partition in a multi-boot system or in VirtualBox but not as the only or primary operating system.
60 • Use old distro, new appimage? (by Somewhat Reticent on 2017-09-08 12:28:50 GMT from United States)
@59 • Perhaps your favorite old distro combined with new appimages (where new is better) would give the best of both?
::
@48 • I would agree that most updates are advertised with little or no explanation (or, therefore, justification). If new software is all compiled for 64-bit hardware, would 32-bit hardware require re-compiling from source? Might be good to have a fairly automated build system.
61 • Most Updates Are Good (by M.Z. on 2017-09-08 21:37:34 GMT from United States)
@48 & @59
"If a user decided to install Ubuntu 10.04 and disable all updates, there is still almost zero chance of getting 'hacked' or being victimized from some corner-case security vulnerabilities."
I think the far better scenario in a case similar to that would be to run a Mint LTS release & use the Mint Update to to filter out everything except security updates & probably level 1 or perhaps level 2 updates, which have virtually no impact on system stability. Why ask for trouble, when you can have important security updates with minimal unneeded ones? Also, I have found many distros from Mint, to Mageia & Debian to be plenty stable, so I'm not sure why you would reject updates altogether. It just seems like a bad idea if you are connected to any network to not at least apply security updates. Other updates can bring nice bug fixes even if no one can be bothered to read about all of them. I do see some sense in not applying fixes that aren't necessary, but applying no updates seems far worse than updating everything blindly.
62 • Poopy Butts and Bleeding Hearts (by Arch Watcher 402563 on 2017-09-08 23:37:15 GMT from United States)
@39 Where can I find PoopyButt, I want to try it. This is DistroWatch.
@48 Here's hoping your heart won't bleed. Linux security hysterics as a big overblown community problem, thank you! I needed a deep belly laugh. Clearly you haven't run OpenELEC with its public root password, or Puppy with its rooted user. Find methods you may like in comments 4 and 63 at
http://distrowatch.com/weekly.php?issue=20151116&mode=67
63 • insecure by design (by tim on 2017-09-10 01:08:42 GMT from United States)
In addition to the examples mentioned (OpenELEC and PuppyLinux), several of the for-RaspberryPi distributions ship with defaults insecure-for-the-sake-of-convenience. PiHole, DietPi...
"Desktop" distributions, in general, seem to ship with way too many unneeded / unwanted services autostarted. Many users probably do no realize, do not care, but the unnecessary autostarts represent wastefulness and potential vulnerability vectors.
64 • Updates / Post # 61 (by Winchester on 2017-09-10 02:48:53 GMT from United States)
The point is that Debian / Ubuntu / Mint etc. will ,as I understand the situation,be phasing out 32-bit support in a few years.
Therefore,at that point,what updates will there be for 32-bit systems using those OS??
That would leave the Gentoo family,the Slackware family,the Puppy Linux family (those using Slackware Packages) ,SliTaz,4M Linux, UpLOS, Mageia, and TinyCore / CorePlus as options for 32-bit machines to receive updates. Maybe a couple of others but,not many.
65 • Still Plenty of Options (by M.Z. on 2017-09-10 20:19:08 GMT from United States)
@64
"The point is that Debian / Ubuntu / Mint etc. will ,as I understand the situation,be phasing out 32-bit support in a few years."
Perhaps my previous post didn't take into account that aspect of the context, but regardless of that, there are plenty of options existing right now & any idea of not applying any updates at all is a very bad notion. Holding back certain updates for the sake of stability is widely practiced in IT & can be the best solution if it is done right; however, running an old vulnerable system on a network is bad for everyone. You would essentially be like an anti-vaxer nut who is hurting herd immunity. In this case that means increasing the vulnerability of everyone else on the web by intentionally leaving a machine networked that is easily co-opted for malicious purposes. It's bad enough when unaware users with old windows machines do that sort of thing, but we are talking about supposedly intelligent Linux users here & they should darn well know that there are options.
Even when I get very picky about how I exclude everything downstream of distros Debian & Ubuntu from a search here on DW just for i386- i686 that are for desktop, beginners & old PCs I come up with over 50 options. I would personally prefer support for non 64 bit desktops for at least a few more release cycles in the Debian family; however, there are plenty of other options. If you are leaving an unsupported version of Debian on some old corner PC that never touches a network & is just there to print documents if your main desktop fails that is fine, but networking an insecure system is just stupid.
It's also worth pointing out here that if you include all the other possible distro categories in a search for non Debian family OSs with i386-i686 support you get an extra 30 or so results for things that you could do with that old PC. In my case I've often reused junk PCs as pfSense based firewalls. That way I actually make myself & everyone else more secure, rather than causing possible problems by networking an insecure machine. There are of course other many possible tasks one could do with such a machine & many could be more satisfying & useful than creating an anemic & insecure desktop. Perhaps you could figure out how to create Network Attached Storage, or just plain play wit some new Distro on an old machine you can afford to mess up.
Number of Comments: 65
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 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 |
| • Issue 1036 (2023-09-11): SDesk 2023.08.12, hiding command line passwords, openSUSE shares contributor survery results, Ubuntu plans seamless disk encryption, GNOME 45 to break extension compatibility |
| • 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 | 
VideoLinux
VideoLinux was a PCLinuxOS-based distribution with focus on DVD backups, video encoding and transcoding, DVD authoring, format conversion and pretty much anything else you want to do with video.
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.
|
|
• 
• 
• 
• 
• 
• 
• 
0x969CD4E778C7b6549A2B00e34114e0168c86A542 
