| DistroWatch Weekly
|DistroWatch Weekly, Issue 772, 16 July 2018
Welcome to this year's 29th issue of DistroWatch Weekly!
One of the joys of open source software is the way the developer community finds all sorts of new and unexpected approaches to solving problems. This week we begin with a review of an unusual distribution which combines packages from Arch with patches from Debian and includes free software only. Read on to learn more about the Hyperbola GNU/Linux-libre distribution. In our News section we talk about work being done to get desktop applications running on the UBports mobile operating system along with a look at reports of malware in the Arch User Repository. Plus we share news that OpenBSD will soon be able to auto-join wireless networks, Debian has updated the distribution's install media and Tails is making it easier to work with encrypted volumes. In our Tips and Tricks column we discuss a new utility for managing ZFS boot environments called zedenv. Boot environments are also the topic of our Opinion Poll and we would like to find out how many of our readers use these powerful snapshots of their operating systems. Plus we share the releases of the past week and provide a list of the torrents we are seeding. We wish you all a wonderful week and happy reading!
- Review: Hyperbola GNU/Linux-libre 0.2.4
- News: UBports running desktop applications, Arch reacts to AUR malware, OpenBSD gaining ability to auto-join wireless networks, Debian publishes new install media, Tails makes it easier to work with encrypted volumes
- Tips and tricks: Managing boot environments with zedenv
- Released last week: Scientific Linux 6.10, ArcoLinux 6.9.1
- Torrent corner: Archman, ArcoLinux, AUSTRIMI, Bluestar, Clonezilla, Debian, feren OS, Greenie, Live Raizo, Pardus Topluluk, ReactOS, Scientific, Ultimate Edition
- Opinion poll: Boot environments
- Reader comments
|Feature Story (by Jesse Smith)
Hyperbola GNU/Linux-libre 0.2.4
Hyperbola GNU/Linux-libre is a curious project that takes a number of interesting approaches which set it apart from other distributions. The Hyperbola distribution is based on snapshots of Arch Linux. While Arch Linux is a rolling release distribution, Hyperbola maintains fixed releases taken from Arch snapshots and then, according to the project's website, the Hyperbola developers mix in security updates from Debian. The idea is to create an Arch-like operating system with a fixed base and minor patch updates.
The distribution is dedicated to free software ideals and ships only libre software as defined by the Free Software Foundation. Finally, Hyperbola makes a special edition called Hypertalking which is based on TalkingArch and provides accessibility software for visually impaired users.
I downloaded the distribution's main edition which is available as a 672MB ISO. The distribution media will boot on both 32-bit and 64-bit systems with the option to select which architecture we want from the ISO's boot menu. When the disc boots we are presented with a text console where we are advised we can see documentation for getting on-line using the Lynx web browser by typing "lynx network.html".
The default, text-based interface on the disc is quite minimal, but it's enough to partition our hard drive and set up a local copy of the operating system. I don't think it's intended to do much more than that.
Instead of providing users with a system installer, Hyperbola follows the example of Arch Linux and provides an on-line install guide. The guide walks us through creating disk partitions, mounting them, making sure a network connection is enabled and setting up security keys. It's a bit of manual work, but for the most part new users will be able to copy the command line examples from the manual into their terminal to get a working system.
The guide concludes by getting us to install packages on our hard drive, set up a language locale, install the GRUB boot loader and create a password for the root user. After that, we can reboot the computer to start exploring Hyperbola. The manual steps are not difficult to follow for people familiar with the command line, but will probably deter Linux newcomers from trying the distribution.
Hyperbola starts off as a minimal operating system. The snapshot I was using ran version 4.9 of the Linux-libre kernel, a flavour of Linux that has had non-free components removed. Instead of Arch's default systemd init software, Hyperbola ships with OpenRC as its init implementation. At the moment, Hyperbola ships with the OpenSSL security library, but there are plans to switch to LibreSSL in a future snapshot.
Otherwise the base system features the standard GNU command line tools, manual packages and little more. There is no compiler, by default, no Java, and no desktop environment. Hyperbola very much holds to the idea that we need to build and customize our operating system from the ground up.
We can add new users to the system via the useradd command and we can use pacman to add new software to the distribution. Hyperbola does not have documentation nearly as extensive as Arch's famous wiki, but we can use most of Arch's documentation on Hyperbola. I say "most" because not everything translates over to Hyperbola's environment. Since Arch allows software published under non-free licenses and uses systemd to manage services, its approach varies in small ways from Hyperbola's. This means some steps in setting up services, trouble-shooting issues and getting a desktop environment set up will be different under Hyperbola. Users should be aware they will need to adjust some examples that use systemd to get them working with the OpenRC service manager and work around not having some packages.
Software and package management
Like its parent, Hyperbola uses the pacman command line package manager to install, remove and upgrade software. pacman works quickly and I encountered no problems while using it. Software appears to all be pulled from the distribution's own collection of custom repository mirrors.
Earlier I mentioned Hyperbola uses an unusual combination of Arch software with Debian patches, which is explained on the distribution's FAQ page: "Hyperbola is a long-term support distribution based on Arch GNU/Linux plus stability and security from Debian GNU/Linux. It isn't a rolling release distribution like Arch because Hyperbola is using Arch snapshots for its versions and Parabola blacklist as base to keep it 100% libre. Also Hyperbola is using Debian patches, therefore all packages are being stabilized with improvements through its development."
I'm not certain of the details of this update process. Arch and Debian name some software differently or may use slightly different versions of packages, leaving me to wonder exactly how patches get transferred from Debian into Hyperbola. At the moment I am not entirely clear on how long Hyperbola's "long-term support" cycle lasts. One might guess for as long as Debian Stable is supported, but I was not clear on this from the documentation provided. At the moment, Hyperbola is still a fairly young project so it may take time before users get a clear idea of the length of support cycles and how many versions will be supported at a time.
At first my trial with Hyperbola started out well. The dual-architecture CD was able to start in on my laptop in both Legacy BIOS and UEFI modes. The distribution, once installed, required less than 50MB of RAM with the default configuration and used around 1GB of disk space. The distribution was wonderfully fast, mostly because it runs so little software by default.
The main issues I ran into revolved around hardware support. When trying to run the distribution on my laptop, Hyperbola was unable to use my wireless network card. Given the situation I was in at the time, this basically turned my laptop into a typewriter as a wired connection was not always available, making it difficult to get on-line or install new software.
When running in VirtualBox, Hyperbola started off well, but ran into a snag with displaying a desktop. The distribution does not appear to include VirtualBox modules and this meant I struggled to get a fully functional desktop working in the virtual machine. Given more time I might have managed, but since setting up Hyperbola takes extra steps (compared to other distributions) I was running short on time to work around the driver issues.
My big concern with Hyperbola was the documentation. We can use the Arch wiki for most tasks, but there are enough little things that are different between Arch and Hyperbola (like using systemd versus OpenRC) that I think this project needs its own fork of the documentation. I also ran into an unfortunate oversight early on. When I launched the distribution on my laptop and found my wireless network wasn't detected, I ran "lynx network.html" to see the steps required to get it working. In the document there is a link to show trouble-shooting steps for when networking does not operate as expected. The link doesn't work because it points to an on-line resource. It is little details like this which will hopefully be addressed in future snapshots.
What drew me into trying Hyperbola is the distribution is just such an unusual mixture of design choices. It tries to be a fixed release, but is based on Arch Linux, a rolling release platform. The distribution tries to be convenient for visually impaired users through its Hypertalking edition, but also slows me down by effectively disabling some hardware devices by not including non-free drivers and firmware.
The distribution wants to be stable, free, near the cutting edge, accessible and minimal. It also pulls in ideas and software from at least four other projects. It's quite an odd combination and as a result I'm not entirely sure what use cases Hyperbola is targeting. People who want a libre distro like Trisquel, but prefer pacman for package management? People who love the manual approach of setting up Arch, but with Debian-like security updates? Hyperbola is so weird I can't help but appreciate it, but I'm not sure under what circumstances I would consider it the best tool for the job.
* * * * *
Hardware used in this review
My physical test equipment for this review was a de-branded HP laptop with the following
- Processor: Intel i3 2.5GHz CPU
- Display: Intel integrated video
- Storage: Western Digital 700GB hard drive
- Memory: 6GB of RAM
- Wired network device: Realtek RTL8101E/RTL8102E PCI Express Fast
- Wireless network device: Realtek RTL8188EE Wireless network card
* * * * *
Visitor supplied rating
Hyperbola GNU/Linux-libre has a visitor supplied average rating of: 10/10 from 1 review(s).
Have you used Hyperbola GNU/Linux-libre? You can leave your own review of the project on our ratings page.
|Miscellaneous News (by Jesse Smith)
UBports running desktop applications, Arch reacts to AUR malware, OpenBSD gaining ability to auto-join wireless networks, Debian publishes new install media, Tails makes it easier to work with encrypted volumes
One of the potential benefits to running a GNU/Linux operating system on a mobile device is it opens the door for running desktop applications on the mobile platform, greatly expanding the numbers of apps available on the device. The UBports community (who have continued the development of Ubuntu Touch) may soon be able to run desktop Ubuntu packages on mobile devices. In a Reddit post, one developer comments on the state of running desktop Ubuntu applications in a container on a UBports phone: "Libertine Manager is now in the system settings and makes installing 'desktop' apps easier (creates a container and installs apps inside with APT). Some apps work better than the others, in the video GNOME Calculator doesn't work that great yet, Solitaire seems to work ok and is quite usable on a phone." The video demonstrating installing desktop apps on the phone is included in the Reddit post.
* * * * *
People who run Arch Linux, or one of its many derivatives, received a reminder last week that while the Arch User Repository (AUR) is a convenient way to access a large number of software packages, the packages in that repository can come from anywhere and should not be blindly trusted. Sensors Tech Forum reports: "Linux users of all distributions have received a major warning not to explicitly trust user-run software repositories following the latest incident related to Arch Linux. The project's user-maintained AUR packages (which stands for Arch User Repository) have been found to host malware code in several instances. Fortunately a code analysis was able to discover the modifications in due time - only several days after the dangerous code was placed in the app installation instructions. The security investigation shows that a malicious user with the nick name xeactor modified in June 7 an orphaned package (software without an active maintainer) called acroraed. The changes included a curl script that downloads and runs a script from a remote site. This installs a persistent software that reconfigures systemd in order to start periodically. While it appears that they are not a serious threat to the security of the infected hosts, the scripts can be manipulated at any time to include arbitrary code. Two other packages were modified in the same manner." Most Linux distribution have optional add-on repositories where community members can upload scripts or packages. These third-party items should be audited before being installed.
* * * * *
The OpenBSD operating system is getting a new feature which many people running on other platforms probably take for granted: automatically connecting to wireless networks. Peter Hessler has published code which allows OpenBSD to connect to known wi-fi networks automatically when there is no current network connection. "Introduce 'auto-join' to the wi-fi 802.11 stack. This allows a system to remember which ESSIDs it wants to connect to, any
relevant security configuration, and switch to it when the network we are
currently connected to is no longer available."
* * * * *
The Debian project has published new install media for Debian 9 "Stretch". The new media does not represent a new version of Debian, but does include security fixes that have become available since Debian 9 was originally released. "The Debian project is pleased to announce the fifth update of its stable distribution Debian 9 (codename Stretch). This point release mainly adds corrections for security issues, along with a few adjustments for serious problems. Security advisories have already been published separately and are referenced where available. Please note that the point release does not constitute a new version of Debian 9 but only updates some of the packages included. There is no need to throw away old stretch media. After installation, packages can be upgraded to the current versions using an up-to-date Debian mirror." More information can be found in the project's news post.
* * * * *
The Tails project is working to make accessing encrypted volumes easier. The developers are a testing new features which would make it easier for users to access VeraCrypt volumes from the GNOME desktop. "We worked to integrate VeraCrypt support into the existing GNOME workflow for unlocking encrypted volumes. As a result, most of the features already provided for LUKS volumes are now also provided for VeraCrypt volumes. This includes unlocking volumes via the GNOME Disks application and integration into the places sidebar in GNOME Files. If your file containers have the ".hc" file extension, they will be recognized as VeraCrypt volumes and can be easily unlocked in GNOME Files. Additionally, we created a small application, VeraCrypt Mounter, which makes it easier to unlock VeraCrypt volumes, especially file containers that do not have the ".hc" extension." The project's news page has further details.
* * * * *
These and other news stories can be found on our Headlines page.
|Tips and Tricks (by Jesse Smith)
Managing boot environments with zedenv
Boot environments are handy tools for a system administrator to have. A boot environment is basically a snapshot (or copy) of the operating system which was taken at a point in time when the operating system was (presumably) working properly. Having a snapshot of the operating system stored on the disk means we can make all kinds of changes to the system, safe in the knowledge that we should be able to revert back to the working snapshot at any time. This means we can update the system, delete files, and change working configurations, safe in the knowledge that we will be able to reboot the computer and switch back to a working snapshot if anything goes wrong.
Boot environments are made possible by advanced file systems, such as Btrfs and ZFS. Typically Btrfs is used on Linux systems (like openSUSE) and ZFS is used by platforms such as FreeBSD. While these advanced file systems provide the underlying ability to create a snapshot of our working system, we still need tools to create and manage the snapshots. On FreeBSD-based systems the beadm command line tool is typically used to manage boot environments. On openSUSE the snapper tool is used.
In May a new, cross-platform boot environment manager was launched. The new tool is called zedenv and is still in its early development stage (it is still considered an alpha release at the time of writing). The zedenv command reportedly supports the same functions and has a similar syntax to beadm, but has the advantage of being designed to work across multiple operating systems and should work anywhere where ZFS and Python are available. The zedenv software also supports plugins which should make it possible to use the same code across a range of operating systems with different boot loaders.
Since I have already used beadm to manage ZFS snapshots on FreeBSD, I thought it would be fun to see if this new utility could manage ZFS boot environments on a Linux distro. This posed a bit of a problem though because very few Linux distributions support running from a ZFS root file system. There are possible workarounds to make Linux boot on ZFS, but most distributions do not offer an easy way to do this. Antergos appears to be one of the few exceptions. So I installed Antergos, opting to run the operating system from a ZFS volume.
Antergos makes it fairly easy to set up a ZFS volume, it is one of the check boxes on the installer's partitioning screen. The process of setting up ZFS takes a while though as the installer needs to build ZFS components, this added around twenty minutes to my install process, during which time the installer appeared to be locked up. However, the process did complete and I happily rebooted the computer to start working with Antergos running on ZFS.
There was a hiccup to overcome first. It appears as though the Antergos installer does not properly export (a special form of unmounting) the ZFS file system after it is set up. This meant my new ZFS root file system (called "mydata") could not be accessed, or "imported", when I first tried to boot my copy of Antergos. Getting a rescue prompt and running the following command worked around the issue:
zpool import -f mydata
From there, I made sure the git source control program was installed so I would be able to set up zedenv.
sudo pacman -Sy git
Then I followed the step-by-step instructions in the zedenv documentation to install the utility.
git clone https://github.com/johnramsden/pyzfscmds
At this point the installation appeared to have succeeded and I thought I should be able to create, list and activate boot environments by running the zedenv command. However, I soon found I was unable to create snapshots using zedenv. I could manually create snapshots using the lower level zfs command, but not new boot environments.
git clone https://github.com/johnramsden/zedenv
sudo python setup.py install
cd ../zedenv pyzfscmds
sudo python setup.py install
With a little trouble-shooting it turned out the problem was zedenv expects ZFS datasets to be created when the file system is set up. FreeBSD does this automatically, but Antergos does not. The zedenv author pointed out there are ways to work around this problem. However, given the nature of changing the ZFS datasets and boot settings, the user will probably want to create backups of their data before attempting the workaround. Long-term, I am hoping the Antergos team will be able to bring their ZFS setup more in line with that of other operating systems.
* * * * *
Speaking of other systems, I also tried zedenv on FreeBSD to see how the utility would compare to the popular beadm boot environment manager. FreeBSD is relatively quick to set up and also makes it possible to just check a box to automate placing the root file system on a ZFS volume.
Once FreeBSD's installation is complete we will need to install three packages to work with zedenv. We will need to install Python 3.6, the git source control tool and the Python setuptools package. These can be added to FreeBSD by running:
pkg install python36 git py36-setuptools
Then I ran the same git and Python commands as I did above to install zedenv on Antergos. At first zedenv failed to run, reporting a series of locale errors. I was able to quiet these errors and get zedenv to run without crashing by setting the LANG shell variable:
setenv LANG en_US.UTF-8
With these steps completed, I was able to create boot environments, list them, and activate them so the system would automatically boot into the one I wanted. The zedenv command also makes it possible to mount an existing environment to edit it. Let's look at an example of the command in use. Here we create a new environment snapshot, called "safe":
zedenv create safe
We can confirm the snapshot was created by listing all our snapshots:
There should be two snapshots listed, with one called "default" which is currently active. The other is the new one we created, called "safe". Now, suppose we did something foolish, like delete a bunch of programs we will need later. For example, suppose I deleted every program starting with the letter "d" in my /bin directory. We can then try to rescue the system by switching from our active (default) file system, to our good snapshot (safe).
zedenv activate safe
When the system reboots, the programs in /bin I recklessly deleted will have been restored because the "safe" snapshot was created before I removed the files. If I want to, I can then try to fix the default boot environment, where I deleted the programs. I can do this by mounting the default boot environment and copying the missing programs into it. This can be done as follows:
zedenv mount default /mnt
With the default snapshot repaired, I can activate it and boot into it again.
cp /bin/d* /mnt/bin/
zedenv umount default
zedenv activate default
Experienced FreeBSD users will note zedenv has a syntax and output virtually identical to beadm. The main differences are zedenv is designed to (hopefully) work the same on other platforms and it can be extended using plugins. Though this extra flexibility does come at the cost of having a dependency on Python.
Right now zedenv works. It does not yet hold an advantage over beadm on FreeBSD, but its goal of cross-platform use certainly sounds promising. I think the only thing holding back zedenv from being a big hit with Linux users is most distributions still have not embraced advanced file systems like ZFS and Btrfs. This will likely change over time, but right now most Linux distributions are still using more traditional file systems like XFS and ext4. It may take a while before boot environments catch on, outside of the openSUSE community.
* * * * *
Additional tips can be found in our Tips and Tricks archive.
|Released Last Week
Scientific Linux 6.10
Pat Riehecky has announced the availability of Scientific Linux 6.10, the final build of the Red Hat-based distribution's legacy branch, supported until November 2020: "Scientific Linux 6.10 i386/x86_64. According to the upstream lifecycle guide, 6.10 is expected to be the final release of EL6, with only important security errata or critical bug fixes going forward. Please run yum clean expire-cache. Major Differences from SL 6.9: sl-release - updated to use the 6.10 repositories; OpenAFS - updated to 184.108.40.206. Changed compared to Enterprise 6: httpd - changed the default index.html to remove upstream's branding; Plymouth - removed the red colors for text mode; redhat-logos - changed all trademarked icons and pictures from upstream, changed styles of items such as background, GDM and KDM to change the tradedress style; Anaconda - add the Scientific Linux install classes, DVD installs do not ask for the network unless needed; redhat-rpm-config - changed to recognize Scientific Linux as an Enterprise Linux; xorg-x11-server - changed to remove TUV's support URL...." See the release announcement and release notes for further information.
ArcoLinux (formerly known as ArchMerge), is an Arch-based project developing several ready-to-use distributions that feature a number of popular desktop environments. ArcoLinux 6.9.1 was pre-announced earlier this week, but the main Xfce edition was only made available yesterday. From the release announcement: "We decided to trim down our ISO images and remove elements we either don't use or which might be considered a security liability. You can install them if you want them after the installation of the ISO image. Our goal is to stay around 2 gigabytes for the ArcoLinux ISO image. Improvements: new logo has been included in the logos of the conkies; font display has been improved and resized to 11; added VMware configuration file to include 1920x1080 resolution; Neofetch has been upgraded from v4 to v5, we follow the official configuration and change it to our own ArcoLinux configuration; 000- script to use all cores now also includes 6 cores; new alias vbm to mount the Public folder when on VirtualBox; old alias 'update' is now 'sudo pacman -Syyu'...."
ArcoLinux 6.9.1 -- The default ArcoLinux desktop
(full image size: 1.5MB, resolution: 1280x1024 pixels)
* * * * *
Development, unannounced and minor bug-fix releases
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: 940
- Total data uploaded: 20.6TB
|Upcoming Releases and Announcements
Summary of expected upcoming releases
This week, in our Tips and Tricks column we discussed how to use a tool called zedenv to manage ZFS boot environments. Some operating systems, such as openSUSE and FreeBSD ship with built-in tools for managing and running the operating system from boot environments - file system snapshots that let us access past states of the operating system.
We would like to know how many of our readers currently use boot environments. And, if you do, which file system are you using?
You can see the results of our previous poll on how people are reacting to CPU security bugs in last week's edition. All previous poll results can be found in our poll archives.
DistroWatch database summary
* * * * *
This concludes this week's issue of DistroWatch Weekly. The next instalment will be published on Monday, 23 July 2018. 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)
If you've enjoyed this week's issue of DistroWatch Weekly, please consider sending us a tip.
(Tips this week: 1, value: US$7.60)
|Linux Foundation Training
|Reader Comments • Jump to last comment
1 • ZFS on Boot (by Will Senn on 2018-07-16 01:17:42 GMT from United States) |
Uh-mazing how few people are doing boot on ZFS here. Far and away my favorite file system. I've been doing FreeBSD on ZFS for about 3 years. No issues, super easy backup/snapshot/restore/remirror/etc. If I could get the same setup on my Mint install, I wouldn't even pause for breath. While timeshift is cool, BTRFS isn't and boot on LFS isn't exactly painless either, otherwise, it might be a similar experience, but between EFI, Grub, and LFS getting a new system restored from timeshift on anything other than a default config is, mmm, ouch.
Fun stuff, thank for bringing it up on DistroWatch.
2 • @ "will probably deter Linux newcomers" (by OS2_user on 2018-07-16 01:47:07 GMT from United States)
That seems to be a key goal of many distros besides comments here. Hyperbola seems to be setting a new standard of deterrence.
Moving on... Today downloaded and installed the Mate version of PCLinux 2018.06. As always, it didn't present native resolution of my 1600x900 monitor -- which I keep because small, tack sharp, very low power, and I got it for $2 at the flea market, apparently nearly new (likely because too small). So, first, no, I'm not throwing it out to replace with one for the convenience of Linux distros rather than them doing it right: query the monitor for available resolutions, and offer the choice in a list. That monitor is a useful practical test, which nearly all distros fail. -- THIS time after hunting, found was able to "configure the X server" and get the resolution listed (believe was after selecting "other"), and then (after required reboot) have the system actually come up with the selected resolution. -- IF stays set, then the "Linux desktop" has now nearly caught up with Windows 2000 in one basic key function, though not nearly so convenient to set.
Anyhoo, that was actually after a repeat of the (Mate) desktop manager completely losing its main function of program start menu, just nothing would pop up except the useless right click choices. -- HOW can KDE and Mate versions fail exactly the same way? Is it ME? Bad attitude? But I never have such fundamental trouble with either Windows or OS/2! (By the way, those both have a watchdog in the desktop managers that re-generate the desktop.) -- HOWEVER, prior experience with PCLinux provided more hope, so I rebooted and continued. -- So far okay... Guess all for now.
3 • Hyperbola (by Ken on 2018-07-16 02:05:23 GMT from United States)
I was someone who gave Hyperbola a try, and I can explain why I thought it was the best choice for me (it wasn't, but I tried it).
My introduction to GNU/Linux was through Linux Mint. Later, being attracted to the Free Software philosophy, but liking the Ubunto-base I was using, I installed Trisquel and used it for a couple years. But Trisquel is extremely slow in upgrading. Trisquel 8, which is based on Ubuntu 16.04, just came out a few months ago--two YEARS after its base was released. Security updates were also slow in coming, so I decided to move to a different FSF-approved distro.
Though I was hesitant to try an Arch-based distro since I only had experience with Ubuntu-based ones, I learned how to manually install Parabola. I replaced Trisquel on both my desktop and my Libreboot laptop, and after a few mi-sstarts (what's learning Arch without a few mistakes along the way, right?) I got two fully functional Parabola installations going.
They ran well for a while, but eventually I hit the snag most Arch users hit -- updates broke my systems. I wasn't as good a troubleshooter back then, but I did manage to get things working again. I was happy with the way my systems worked--when they worked. When they didn't, it was a pain to get them working again. Since Parabola is bleeding edge, things are almost sure to go wrong eventually.
When I heard about Hyperbola, I thought this might be for me: Arch-based but much slower updates for better stability, completely Free Software, access to the AUR, non-systemd (can't hurt, right?). I tried it out, but found too many things missing I thought I would have, and the experience was buggy--some things just plain didn't work. I couldn't even get the OpenRC version at the time to install on my desktop.
After only a short time I switched my laptop back to Parabola, and haven't had any problems since. Wanting a little more stability on my desktop, just in case something breaks in Parabola and I need my other computer to sort it out, I currently have a custom Manjaro installation that is as Free as I can make it. Maybe I'll give Hyperbola a look again some day, but for now, it fails in providing the experience I'd hoped for.
4 • For comparison: system backup in OS/2. (by OS2_user on 2018-07-16 02:20:38 GMT from United States)
Requires only about 500M, and it's easiest if boot volume is a separate couple gigabytes, else you'd need to write a script listing just system and program directories. -- For last 5 years I've been using a 1G solid-state SATA that plugs into M/B. Religiously backup, but never needed.
So: 1) Make a bootable volume by using LVM on command line. 2) While the system is running normally XCOPY * (with switches) to it. -- In less than 5 minutes (xcopy is SLOW compared to normal copy) you're done, though hardware swaps are needed to actually use: will come up exactly same with whatever programs on the drive. Can easily restore any given files too.
5 • Tech & Texstar (by PC Doc on 2018-07-16 02:20:57 GMT from Australia)
The tech / hacker culture has brought us troubles like drive-bys, viruses, injections, exploits, back-doors, trojans, spying, etc. But one good thing is that it keeps us alert, on our toes, observing, checking, testing, and patching our PCs.
This is necessary in health too: being alert, observing, checking, and patching our bodies to early-detect problems like cancer. So a big thanks to the tech / hacker community - who inadvertently remind us of this necessary type of activity (and help us to live longer). Let's hope that Texstar gets a break with his checkups, and lives longer too.
6 • Hardware issues (by Jon Wright on 2018-07-16 03:49:43 GMT from Vietnam)
I'm a fan of low-resource distros and 50MB is notably low.
I'm sure it's possible to get a USB wifi dongle with Linux-friendly chipset for $5-10? If so any issues with non-supported drivers are simply moot? Constant dwelling on hardware issues in DW reviews becomes monotonous and oh-so predictable.
> "The distribution tries to be convenient for visually impaired users"
Linux Mint, please take note. This once-friendly distro is fast headed into hardcore-geek territory with its refusal to adhere to basic readability considerations. It's not as if I'm *that* old. (Typing this in grey-on-white, Mint19 XFCE.)
7 • File Systems and TAILS (by cykodrone on 2018-07-16 13:37:58 GMT from Canada)
I am old school, I will use tried and tested file systems, whatever is the default in my NON systemd installs.
If somebody doesn't make a systemd free TAILS soon, I just may just do it myself, I do not trust any RH written spyware to have root permissions to access my drives, especially encrypted drives. RH has many contracts with numerous gov agencies, you can call me a paranoid alarmist if you want, I'm OK with that.
8 • 50M (by John on 2018-07-16 13:47:01 GMT from United States)
Overbloat is here. I still use DSL. 50Meg and plenty overbloated.
John NH USA
9 • TAILS (by Jon Wright on 2018-07-16 13:48:35 GMT from Vietnam)
> "If somebody doesn't make a systemd free TAILS soon"
10 • @9 Re Heads (by cykodrone on 2018-07-16 14:34:58 GMT from Canada)
Thank you, you made my day, nice to see there IS an alternative to TAILS. :)
11 • @6 about wifi dongle (by SA on 2018-07-16 17:03:39 GMT from France)
Hello, I found that wifi dongles sold as "compatible with Raspberry Pi" work well (for what I've seen) with Linux (not only with ARM scomputers)
I couldn't find other that worked and easy to buy, in my country.
12 • Freedom in Software & Distro Visions (by M.Z. on 2018-07-16 17:29:07 GMT from United States)
'...setting a new standard of deterrence.'
It's a young distro without a desktop. That sort of complex OS has existed from the time that OSs were first created.
Why not accept the fact that people have different visions for the versions of Linux they create?
Newcomers to Linux who want an easy desktop are always welcome to try Linux Mint, PCLinuxOS, etc. & those that want to dig deep into the innards of an OS can try working the Linux From Scratch DIY manual. These projects all exist in a vast community of Linux & BSD flavors, and they are all free to target any users they want. If an adequate user base for the distro exists, then the distro will continue.
All the masses of users hungering for an operating system that makes them feel free deserve a distro that meets their needs, expectations & vision for the type of computing they want to do. That includes easy desktop distros, home firewall & NAS OSs, & complex systems for learning how an OS works. Why not encourage them to be free to follow their individual vision of freedom & happiness in computing?
13 • « audited » (by Donald Trump on 2018-07-16 20:06:51 GMT from France)
From the AUR malware part :
> These third-party items should be audited before being installed
I am not very advanced, someone can explain to me how « audited » ?
Thank you by advance.
14 • @2; @12 ... "will probably deter Linux newcomers" (by R. Cain on 2018-07-16 22:26:46 GMT from United States)
*How to Upgrade to Linux Mint 19* blog, 4 July, of Mint Linux with its almost six hundred complaints about Mint19 also "...will probably deter Linux newcomers". Some are about multiple, serious system-administrator-level problems; and most are obviously from previous users. Mint used to be the acknowledged "ease-of-installation" champion for the new Linux user, the "I'd give this to my grandmother" distro.
@12--"...Why not accept the fact that people have different visions for the versions of Linux they create...?"
The problem is that the vision changes, right in mid-stream, where you'd NEVER expect it to. Mint's creator used to be proud of his statement that he would not ship a version "...until it is ready..." (his words).
15 • @ « audited » (by Donald Trump on 2018-07-16 20:06:51 GMT from France) (by someguy on 2018-07-16 23:40:48 GMT from Australia)
Users need to inspect the PKGBUILD file to understand what it it will do to your system.
The issue is that a lot of people use AUR helpers that make skipping this step trivial, hence they easily get malware.
16 • "Will probably deter Linux newcomers"..... (by Az4x4 on 2018-07-17 01:46:42 GMT from United States)
@14... "will probably deter Linux newcomers" (by R. Cain on 2018-07-16 22:26:46 GMT from United States)
"*.....Mint Linux with its almost six hundred complaints about Mint19 also '...will probably deter Linux newcomers'. Some are about multiple, serious system-administrator-level problems; and most are obviously from previous users. Mint used to be the acknowledged 'ease-of-installation' champion for the new Linux user, the "I'd give this to my grandmother" distro."
That's one of the hazards]developing based on someone else's upstream work -- which after all is what distro developers do.
I'm one of the long time Mint users who pointed out the obvious, that this first release of Mint 19 falls short in certain areas, the most troubling in my case being that Wine 3.x won't display a working 'Wine' menu when it's installed, making using it more cumbersome and indirect than it should be. But this isn't a problem originating with Linux Mint, it's a problem originating with WineHQ that effects Ubuntu 18.04 and distros based on Ubuntu, including of course Linux Mint 19.
As far as overall ease of installation and use, Mint 19 is entirely up to par in most instances and does most things as flawlessly as ever. Once upstream issues like Wine not installing a working menu have been ironed out, the Mint 19.x series of releases will doubtless be as accomplished a desktop Linux OS as the Mint 18.x series has been -- far and away the best of the bunch with it comes to a Debian-Ubuntu based desktop operating system.
17 • @16 "Will probably deter Linux newcomers". (by pengxiun on 2018-07-17 03:09:33 GMT from New Zealand)
" That's one of the hazards]developing based on someone else's upstream work -- which after all is what distro developers do. "
Failed install while still connected to the net at grub install process.
"The 'grub-efi-amd64-signed package' failed to install into /target/."
"Fix" is to disconnect from the internet and re-run the install.
This is a current problem, that is carried over from previous releases.
Apparently, this is an "upstream" problem.
Then there are updates which bork the system. ie. virtual-box graphics driver, which, even if you are on real hardware without virtual-box installed, was installed as it is a dependency.
Again, response is to blame "upstream" and to advise the affected users to issue some terminal commands to revert the offending update
Pointing the finger of blame at "upstream" does not endear you to "upstream" and certainly gives the impression of a less than professional response, after all, you, The Mint Team, have declared "fit for purpose" by releasing your current Mint O/S and allowing any updates.
Mint mantra was "release when ready", obviously that has gone by the board, now it seems to be "Ubuntu released last month, lets get this thing outta here".
The reality is, these are Mint problems, as viewed by the user, not "upstream", and probably is part of the reason for Mints fall from #1 on Distrowatch DHR.
I note that Mint is now at best #2 for all meaningful periods.
Because of the above, I no longer recommend Mint or even Ubuntu derivatives.
18 • @9 Tails alternative (by aguador on 2018-07-17 05:50:27 GMT from Netherlands)
You made MY day: an TAILS alternative without GNOME!
19 • "will probably deter Linux newcomers" (by R. Cain on 2018-07-17 08:51:13 GMT from United States)
"...So yes, in many aspects, Tara works better than the competition. But the competition is awful...[with] Unnecessary, pointless [problems]. Even more so because we didn't have them in the past. These are regressions. Horrible, life- and will-sapping regressions..."
--dedoimedo, 'Linux Mint 19 Tara - Tara Cognita'
In the past, in the time before horrible life-sapping and will-sapping regressions, 'systemd' was not used. Now it is used by all of Tara and all of its competition.
20 • AUR and systemd (by Arghalhuas on 2018-07-17 12:58:59 GMT from Spain)
So, are Arch users expected to audit every package and its dependencies prior to installation...? Maybe also take a look to the sources?
The Arch issue illustrates the facts that systemd is not an init system and that it represents a security liability.
21 • Post # 2 : Monitors with Linux (by Winchester on 2018-07-17 14:41:51 GMT from United States)
Don't throw out the off-brand 1600x900 monitor from the flea market to "replace with one for the convenience of Linux distros".
I would recommend doing it simply for the sake of having a better monitor. One with a better resolution. Which would likely make your life easier regardless of any operating system that you choose.
Doesn't using a small monitor defeat half of the purpose of using a desktop computer in the first place???
Low power?? Maybe low but,if it is from a flea market and 1600x900 resolution,I am willing to bet that it uses a CCFL backlight ...... which are less energy efficient than the monitors out there now with various LED backlights ; OLED backlights etc. Available new for less than $ 90 at 1920x1080. Or available for less than that second hand. Some of them are also "sharp as a tack".
However,maybe you are right to say that Windows 2000 is easier to set-up for a 1600x900 low resolution monitor. If you want to use such an operating system for the convenience of a 1600x900 monitor,then don't let me stop you. It just doesn't seem rational,nor does it seem like a wise approach in my opinion.
22 • Hyberbola (by RJA on 2018-07-17 17:56:24 GMT from United States)
@2 ->" Hyperbola seems to be setting a new standard of deterrence." -> Sorry, I disagree, their release model reduces the chance of breakage and is a refuge from people who hate Windows 10.
While yes, their documentation is limited, strangely, seems to demand that I have a static IP, LOL.
23 • @20 AUR (by Ken on 2018-07-17 20:23:04 GMT from United States)
Yes. The AUR front page says in big bold letters: "DISCLAIMER: AUR packages are user produced content. Any use of the provided files is at your own risk." The wiki page for installing AUR packages says in a brightly colored text box: "Warning: Carefully check all files. Carefully check the PKGBUILD and any .install file for malicious commands. PKGBUILDs are bash scripts containing functions to be executed by makepkg: these functions can contain any valid commands or Bash syntax, so it is totally possible for a PKGBUILD to contain dangerous commands through malice or ignorance on the part of the author. Since makepkg uses fakeroot (and should never be run as root), there is some level of protection but you should never count on it. If in doubt, do not build the package and seek advice on the forums or mailing list."
Unlike a traditional distro repository that is locked, maintained by certain maintainers, and audited before packages are accepted, the AUR is an open repository where anyone in the community can upload PKGBUILDS for others to use. It is by its very nature more susceptible to malicious content. That's why Arch warns users that before building any package from the AUR they should either already trust the contributor or audit the code themselves.
24 • @23 (by someguy on 2018-07-18 00:53:34 GMT from Australia)
Exactly, this is also why Arch users get annoyed with Manjaro users. Manjaro comes with an AUR helper pre-installed and somewhat obfuscates the risks and the correct use of the AUR.
25 • "...will probably deter Linux newcomers" (by R. Cain on 2018-07-18 04:00:48 GMT from United States)
A *really* good read:
_OCS Magazine_, 10/19/2016--"Systemd – Progress Through Complexity”.
Some snippets for you---
“...The topic...today is to tell you a story of how I went about fixing a broken Fedora 24 system – powered by systemd of course, and why...[the end] was one of pain and defeat...”
“...This led me to a troubling realization that the documentation and general knowledge on Systemd are very rare. There just isn’t the abundance of tips and tricks like you could find on System V, which would help you almost immediately narrow down your problem and resolve it...The reason is quite simple though – Systemd is too complex for its own good and everyone forced to use it...”
”...my Fedora box remained unbootable, and I was forced to rebuild the installation. I do not recall a single case where I was unable to fix a Linux box when it was still powered by good ole [sysv]init. I had worked on some really bad issues, but I was always able to recover. With Systemd, I had to concede defeat. The notion of events and timeouts is just completely wrong...”
“...As far as Systemd is concerned, I *am* concerned, because it is a technology that does not correlate to knowledge or experience, and it poses a great risk to the prosperity of Linux...”
“...you might as well practice Linux installations, since they may be the answer to when Systemd goes bad, as I cannot foresee any easy, helpful way out of trouble. ..”
26 • @2 Monitor Issues (by Archdevil on 2018-07-18 06:04:16 GMT from Netherlands)
I have never had issues on my laptop, that uses a 1600x900 display. I believe the problem lies in the fact that your monitor has issues telling the OS which resolution it prefers. I had the same issues with a Belinea-monitor in the past. A colleague of mine wanted to use it running Windows 7, but we needed special drivers for it to be detected correctly. Same thing may be happening with your monitor.
27 • Slackware turns 25 (by linuxuser on 2018-07-18 07:12:17 GMT from Greece)
Happy 25th anniversary to the Slackware 1.00 release! Congratulations!
28 • @27 (by kc1di on 2018-07-18 12:31:47 GMT from United States)
++1 Happy 25th :)
29 • Hyperbola network troubleshooting docs (by curious on 2018-07-18 13:18:47 GMT from Germany)
In the review, Jesse notes that "In the document there is a link to show trouble-shooting steps for when networking does not operate as expected. The link doesn't work because it points to an on-line resource."
This reminds me of the old practical joke that is present in all BIOSes for when the keyboard is not connected:
"Keyboard error. Press F1 to continue."
Obviously, the way to trouble-shoot totally "libre" distros that must not have the drivers necessary for common wireless network hardware is to install a different distro that emphasises usability instead of FSF guidelines.
The alternative of blocking a USB port with unnecessary extra hardware is unappealing - one always needs at least one more USB port than is available ...
30 • @17 • @16 "Will probably deter Linux newcomers". (by pengxiun on 2018-07-17 (by Az4x4 on 2018-07-18 19:57:07 GMT from United States)
"That's one of the hazards of developing based on someone else's upstream work -- which after all is what distro developers do."
Failed install while still connected to the net at grub install process.
"The 'grub-efi-amd64-signed package' failed to install into /target/."
"Fix" is to disconnect from the internet and re-run the install.
This is a current problem, that is carried over from previous releases.
Apparently, this is an "upstream" problem.
.....Pointing the finger of blame at "upstream" does not endear you to "upstream" and certainly gives the impression of a less than professional response.....
The reality is, these are Mint problems, as viewed by the user, not 'upstream'
Inexperienced users may indeed view any problem they run into with a given distro as somehow originating with that distro itself, demonstrating a deep misunderstanding of the process development teams go through in preparing their distro for general use.
Mint, for example, bases its work on Ubuntu's latest LTS release -- presently Ubuntu 18.04. Ubuntu in turn bases its development work on the latest Debian release. And both of these 'upstream' projects from which Mint draws incorporate not only in house developed bits, but bits from outside their control -- for example the Wine 3 issues that WineHQ has yet to address.
Do they work at mitigating regressions and bugs in putting their projects together? Of course they do. Are they successful 100% of the time? ..No way.
The good as well as the not so good flows downhill to projects like Linux Mint. And until they're 'fixed' upstream, downstream projects based on less than perfect upstream releases are affected just like their parent project is.
So, yeah, ..the easy thing to do, and many users do it, is to 'blame' downstream releases like Mint for upstream issues inherited from their parent projects.
Once Mint 19.2 and 19.3 are released we'll see the corrections necessary to move the Mint 19.x project forward in the near flawless manner multiple millions of users world wide have come to expect of Linux Mint.
In the meantime Linux Mint 18.3 remains the best of the best when it comes to a Debian/Ubuntu based desktop OS. And it'll be updated until 2021, giving those who wish to do so more than adequate time to make their move to Mint 19.x.
For those who wish to try something new, Manjaro Linux, based on Arch, is interesting to install and play with. There are some serious issues with it as well, but for the moment it's the most popular Arch based distro available and well worth a look..
Other than that, take your pick! Out of the hundreds of desktop distros available there's any number that might float your boat, so enjoy!!..
31 • systemd and mint (by edcoolio on 2018-07-19 09:22:27 GMT from United States)
Systemd? Honestly, I have never had a problem with it and my personal opinion is that accusations of "security issues" is way overblown. Big time.
It has been stable and has become ubiquitous. I'm cool with it.
As for Mint, my opinion is that it has turned into a trainwreck. A bloated distro, loaded with crapware, serious functional issues (we don't need no stinkin' WINE!) and a general air of Windows Wannabe Syndrome. What a shame, but they sure got the latest update out quickly!
A while back, my sisters small children needed a computer that was reliable and had an unbreakable OS, yet easy to use. Of course, loving Mint at the time, I slapped it on there. Recently, I removed Mint and installed MX 17.1.
Clean, fast, no massive bloat, no time-crap popups... oh yeah, no systemd either, only sysvinit. Kinda. Sorta. Systemd is on there for dependencies. See? I'm agnostic about the whole thing and the Linux Gods are smiling.
32 • Linux Mint still great (by Johannes on 2018-07-19 10:23:13 GMT from Germany)
@17 and @16
I also ran into the GRUB error while installing Mint 19 Tara and it cost me a few hours to find the solution (disconnect from the Internet!).
But still, Mint is a stable platform, usable in production. It can work for years on a machine, the updates are well tested, it is simply productive. And unfortunately, there are only a handful of those really stable distros. So apart of some details, I don't see reasons to spit on Linux Mint, as they are doing an excellent job.
33 • @31 • systemd and mint (by edcoolio on 2018-07-19 (by Az4x4 on 2018-07-19 17:48:03 GMT from United States)
"Systemd? Honestly, I have never had a problem with it and my personal opinion is that accusations of "security issues" is way overblown. Big time.
"It has been stable and has become ubiquitous. I'm cool with it."
I'm with you regarding Systemd, sufficiently 'cool with it' not to get worked into a lather moaning about it's supposed issues.
"As for Mint, my opinion is that it has turned into a trainwreck. A bloated distro, loaded with crapware, serious functional issues (we don't need no stinkin' WINE!) and a general air of Windows Wannabe Syndrome....."
Gotta admit I too was disappointed with Mint 19 when I first installed it. Not sure I'd call it a 'train wreck', but this first 19 series release certainly felt like a sub-par release.
Some of that had to do with 'upstream' issues inherited from Ubuntu/Debian, and some boiled down to design decisions which hopefully will be revisited prior to 19.2 seeing the light of day.
This latest Mint release felt a bit like what we used to deal with back in the day when a new Windows release was what we waited for. Windows releases were always more a disappointment than we initially hoped for, once we had them installed and in use.
That sort of release disappointment is so out of character for Linux Mint that it's kind of hard to swallow. I honestly believe Clem and his team will iron these issues out and Mint 19.2 and 19.3 will again showcase the worlds most popular Ubuntu/Debian based desktop distro in its true light.
For what it's worth I'm running Linux Lite 4.0 in a Virtualbox and loving it. For new Linux users looking for a well designed easy to install and use desktop distro that'll do everything they have in mind, Linux Lite is tough to beat!..
34 • Linux Mint 19 (by jaws222 on 2018-07-19 18:29:54 GMT from United States)
I installed Mint 19 XFCE the day after it came out. it's fast and works as usual, except for the PlayonLinux/Office issue which is plaguing all Ubuntu derivatives. Once that gets figured out it will be perfect IMO.
35 • Systemd blows (init.d away) (by CS on 2018-07-19 19:06:35 GMT from United States)
I've never had a problem with systemd either.
Change my mind!
36 • #35 systemd (by vern on 2018-07-19 22:38:29 GMT from United States)
Their trying to change your mind, or convince themselves otherwise. I never had issue with systemd and I would miss its message uses. Why try and revive a dead "house" anyway. Just use systemd, journal and be on with it.
If you prefer the old init system, then just use. Stop trying to convince the rest of us to switch. It AIN'T going to happen.
37 • Upstream-- (by mchlbk on 2018-07-20 06:45:16 GMT from Denmark)
Blaming your issues on upstream is ridiculous.
The point of making a distro is to take something and make it better. If you don't make it better, your distro is a failure.
If it ain't broke - don't fix it. And if it ain't fixed - don't release it.
38 • Tara & Trolls (by frisbee on 2018-07-20 11:48:24 GMT from Switzerland)
@ OS2_user: PLEASE, PLEASE, PLEASE stop trolling. You a source of „Fake News“ as long as their is OS/2, Windows or Distrowatch!
OS/2 is dead. Since 2006. It is obsolete and useless unless you use computers from 90‘s. Even succesor Ecomstation is as good as dead.
@ Winchester and others reading OS2_user posts: just ignore his posts. All he can do is praise the obsolete OS/2 and Windows. Never any valid arguments, just trolling. You can check Distrowatch archives.
@ pengxiun and all others: EVERY system has some HW issues, no matter is it Linux, Windows or even Mac (where everything is controlled and supposed to come from „one hand“).
You get yourself a brand new, shiny Asus ZenBook 13 UX331UAL and Windows 1803 does not install.
Check https://www.heise.de/ct/artikel/Notebook-Test-Asus-ZenBook-13-Wiegt-wenig-laeuft-lang-4108508.html if you don‘t believe. Just one of thousands examples.
@ Dedoimedo readers who take all he sais for granted: Once it was a source of interseting articles. More and more often getting a source of „Fake News“, desinformation and purly subjective views.
Mint 19 Tara is just fine. It has some inherited bugs and there is nothing to do about. Why? Because it’s Linux. There are GTK2 & 3, QT4 & 5, ... countless frameworks and applications mixed in there and only way to change it, is to get it all under a serious company (which will try to earn money with it and tell what is „right for you„) or, you rewrite it all on your own for your own distribution.
All important things work in Tara.
- Installs fine and HW recognition is as good as ever.
- Multimedia works out of the box (MP3 & MP4).
- Wine (3.0) over PlayOnLinux works.
- VirtualBox works just fine.
You don‘t like the default Theme? Get yourself another one or write yourself your own.
39 • @36 vern: (by dragonmouth on 2018-07-20 12:43:26 GMT from United States)
Why don't you take your own advice and quit trying to convince everybody that systemd is The Greatest Thing Since Sliced Bread. If you like it, use it. Let others use what they will.
40 • @38 Tara "just fine" (by curious on 2018-07-20 12:47:14 GMT from Germany)
Mint 19 Tara may be "just fine", especially compared to some of the more user-unfriendly distros out there.
But I think the reason for a lot of the complaints is that Mint used to be *better* than "just fine". Mint 17 was definitely excellent. The versions before 17 also were generally praised a lot. And Mint 18 was also very good, though I haven't seen any compelling improvement over 17 except for it being "newer".
Now, for version 19, you have to emphasize that "all important things work in Tara", as if that were something very special. It is not - it is in fact less than what Mint users have come to expect, which is why many people appear to be disappointed.
41 • Welcome to the DW asylum (by Willie Buck Merle on 2018-07-20 13:05:37 GMT from United States)
Well, the antiSystemDers can whine as much as they wish because the linux-desktop really ain't what linux is best at or used for the most. If you can install ANY desktop version without much fussing-about that is a VICTORY indeed... take it.
As far as security concerns the points are well-taken... BUT going all the way back to OS/2 or PowerPC chips for a solution to those problems? LOL! Get the rubber room ready. I better appreciate the steps FORWARD like patches instead of obsolete hw/sw.
Lastly, perhaps the poll on boot environments could use "I am using the bootCD PE environments for troubleshooting" cuz that's what first came to my thinking.
42 • About "Opinion poll" (by Yuri on 2018-07-20 12:05:44 GMT from Russian Federation)
what do you mean "I am using boot environments with another file system"?
43 • Boot environments (by Jesse on 2018-07-20 13:43:25 GMT from Canada)
@42: I think you could rig up other file systems which use snapshots to work with boot environments. HAMMER, for example.
44 • @ 40 (by frisbee on 2018-07-20 15:01:34 GMT from Switzerland)
What did you expect from Tara, except that it „just works“?
Mint 19 is just fine, same as 18, same as 17 ... All that worked before, still works exactly the same way and it even got some new feathures like Timeshift, which can even be used without some sucidal file formats like BTRFS.
It simply does what‘s made for — so, what exactly is missing or not working in Tara that was better under Qiana?
Number of Comments: 44
|• Issue 772 (2018-07-16): Hyperbola GNU/Linux-libre 0.2.4, UBports running desktop applications, OpenBSD auto-joins wi-fi networks, boot environments and zedenv|
|• Issue 771 (2018-07-09): Linux Lite 4.0, checking CPUs for bugs, configuring GRUB, Mint upgrade instructions, SUSE acquired by EQT|
|• Issue 770 (2018-07-02): Linux Mint 19, Solus polishes desktop experience, MintBox Mini 2, changes to Fedora's installer|
|• Issue 769 (2018-06-25): BunsenLabs Helium, counting Ubuntu users, UBports upgrading to 16.04, Fedora CoreOS, FreeBSD turns 25|
|• Issue 768 (2018-06-18): Devuan 2.0.0, using pkgsrc to manage software, the NOVA filesystem, OpenBSD handles successful cron output|
|• Issue 767 (2018-06-11): Android-x86 7.1-r1, transferring files over OpenSSH with pipes, LFS with Debian package management, Haiku ports LibreOffice|
|• Issue 766 (2018-06-04): openSUSE 15, overview of file system links, Manjaro updates Pamac, ReactOS builds itself, Bodhi closes forums|
|• Issue 765 (2018-05-28): Pop!_OS 18.04, gathering system information, Haiku unifying ARM builds, Solus resumes control of Budgie|
|• Issue 764 (2018-05-21): DragonFly BSD 5.2.0, Tails works on persistent packages, Ubuntu plans new features, finding services affected by an update|
|• Issue 763 (2018-05-14): Fedora 28, Debian compatibility coming to Chrome OS, malware found in some Snaps, Debian's many flavours|
|• Issue 762 (2018-05-07): TrueOS 18.03, live upgrading Raspbian, Mint plans future releases, HardenedBSD to switch back to OpenSSL|
|• Issue 761 (2018-04-30): Ubuntu 18.04, accessing ZFS snapshots, UBports to run on Librem 5 phones, Slackware makes PulseAudio optional|
|• Issue 760 (2018-04-23): Chakra 2017.10, using systemd to hide files, Netrunner's ARM edition, Debian 10 roadmap, Microsoft develops Linux-based OS|
|• Issue 759 (2018-04-16): Neptune 5.0, building containers with Red Hat, antiX introduces Sid edition, fixing filenames on the command line|
|• Issue 758 (2018-04-09): Sortix 1.0, openSUSE's Transactional Updates, Fedora phasing out Python 2, locating portable packages|
|• Issue 757 (2018-04-02): Gatter Linux 0.8, the UNIX and Linux System Administration Handbook, Red Hat turns 25, super long term support kernels|
|• Issue 756 (2018-03-26): NuTyX 10.0, Neptune supplies Debian users with Plasma 5.12, SolydXK on a Raspberry Pi, SysV init development|
|• Issue 755 (2018-03-19): Learning with ArchMerge and Linux Academy, Librem 5 runs Plasma Mobile, Cinnamon gets performance boost|
|• Issue 754 (2018-03-12): Reviewing Sabayon and Antergos, the growing Linux kernel, BSDs getting CPU bug fixes, Manjaro builds for ARM devices|
|• Issue 753 (2018-03-05): Enso OS 0.2, KDE Plasma 5.12 features, MX Linux prepares new features, interview with MidnightBSD's founder|
|• Issue 752 (2018-02-26): OviOS 2.31, performing off-line upgrades, elementary OS's new installer, UBports gets test devices, Redcore team improves security|
|• Issue 751 (2018-02-19): DietPi 6.1, testing KDE's Plasma Mobile, Nitrux packages AppImage in default install, Solus experiments with Wayland|
|• Issue 750 (2018-02-12): Solus 3, getting Deb packages upstream to Debian, NetBSD security update, elementary OS explores AppCentre changes|
|• Issue 749 (2018-02-05): Freespire 3 and Linspire 7.0, misunderstandings about Wayland, Xorg and Mir, Korora slows release schedule, Red Hat purchases CoreOS|
|• Issue 748 (2018-01-29): siduction 2018.1.0, SolydXK 32-bit editions, building an Ubuntu robot, desktop-friendly Debian options|
|• Issue 747 (2018-01-22): Ubuntu MATE 17.10, recovering open files, creating a new distribution, KDE focusing on Wayland features|
|• Issue 746 (2018-01-15): deepin 15.5, openSUSE's YaST improvements, new Ubuntu 17.10 media, details on Spectre and Meltdown bugs|
|• Issue 745 (2018-01-08): GhostBSD 11.1, Linspire and Freespire return, wide-spread CPU bugs patched, adding AppImage launchers to the application menu|
|• Issue 744 (2018-01-01): MX Linux 17, Ubuntu pulls media over BIOS bug, PureOS gets endorsed by the FSF, openSUSE plays with kernel boot splash screens|
|• Issue 743 (2017-12-18): Daphile 17.09, tools for rescuing files, Fedora Modular Server delayed, Sparky adds ARM support, Slax to better support wireless networking|
|• Issue 742 (2017-12-11): heads 0.3.1, improvements coming to Tails, Void tutorials, Ubuntu phasing out Python 2, manipulating images from the command line|
|• Issue 741 (2017-12-04): Pop!_OS 17.10, openSUSE Tumbleweed snapshots, installing Q4OS on a Windows partition, using the at command|
|• Issue 740 (2017-11-27): Artix Linux, Unity spin of Ubuntu, Nitrux swaps Snaps for AppImage, getting better battery life on Linux|
|• Issue 739 (2017-11-20): Fedora 27, cross-distro software ports, Ubuntu on Samsung phones, Red Hat supports ARM, Parabola continues 32-bit support|
|• Issue 738 (2017-11-13): SparkyLinux 5.1, rumours about spyware, Slax considers init software, Arch drops 32-bit packages, overview of LineageOS|
|• Issue 737 (2017-11-06): BeeFree OS 18.1.2, quick tips to fix common problems, Slax returning, Solus plans MATE and software management improvements|
|• Issue 736 (2017-10-30): Ubuntu 17.10, "what if" security questions, Linux Mint to support Flatpak, NetBSD kernel memory protection|
|• Issue 735 (2017-10-23): ArchLabs Minimo, building software with Ravenports, WPA security patch, Parabola creates OpenRC spin|
|• Issue 734 (2017-10-16): Star 1.0.1, running the Linux-libre kernel, Ubuntu MATE experiments with snaps, Debian releases new install media, Purism reaches funding goal|
|• Issue 733 (2017-10-09): KaOS 2017.09, 32-bit prematurely obsoleted, Qubes security features, IPFire updates Apache|
|• Issue 732 (2017-10-02): ClonOS, reducing Snap package size, Ubuntu dropping 32-bit Desktop, partitioning disks for ZFS|
|• Issue 731 (2017-09-25): BackSlash Linux Olaf, W3C adding DRM to web standards, Wayland support arrives in Mir, Debian experimenting with AppArmor|
|• Issue 730 (2017-09-18): Mageia 6, running a completely free OS, HAMMER2 file system in DragonFly BSD's installer, Manjaro to ship pre-installed on laptops|
|• Issue 729 (2017-09-11): Parabola GNU/Linux-libre, running Plex Media Server on a Raspberry Pi, Tails feature roadmap, a cross-platform ports build system|
|• Issue 728 (2017-09-04): Nitrux 1.0.2, SUSE creates new community repository, remote desktop tools for GNOME on Wayland, using Void source packages|
|• Issue 727 (2017-08-28): Cucumber Linux 1.0, using Flatpak vs Snap, GNOME previews Settings panel, SUSE reaffirms commitment to Btrfs|
|• Issue 726 (2017-08-21): Redcore Linux 1706, Solus adds Snap support, KaOS getting hardened kernel, rolling releases and BSD|
|• Issue 725 (2017-08-14): openSUSE 42.3, Debian considers Flatpak for backports, changes coming to Ubuntu 17.10, the state of gaming on Linux|
|• Issue 724 (2017-08-07): SwagArch 2017.06, Myths about Unity, Mir and Ubuntu Touch, Manjaro OpenRC becomes its own distro, Debian debates future of live ISOs|
|• Issue 723 (2017-07-31): UBOS 11, transferring packages between systems, Ubuntu MATE's HUD, GNUstep releases first update in seven years|
|• Issue 722 (2017-07-24): Calculate Linux 17.6, logging sudo usage, Remix OS discontinued, interview with Chris Lamb, Debian 9.1 released|
|• Issue 721 (2017-07-17): Fedora 26, finding source based distributions, installing DragonFly BSD using Orca, Yunit packages ported to Ubuntu 16.04|
|• Full list of all issues|
|Random Distribution |
Subgraph OS is a Debian-based Linux distribution which provides several security, anonymous web browsing and hardening features. Subgraph OS uses a hardened Linux kernel, application firewall to block specific executables from accessing the network and forces all Internet traffic through the Tor network. The distribution's file manager features tools to remove meta-data from files and integrates with the OnionShare file sharing application. The Icedove e-mail client is set up to automatically work with Enigmail for encrypting e-mails.