 DistroWatch Weekly |
| Tip Jar |
If you've enjoyed this week's issue of DistroWatch Weekly, please consider sending us a tip.
(Tips this week: 0, value: US$0.00) |
|
|
|
 bc1qxes3k2wq3uqzr074tkwwjmwfe63z70gwzfu4lx  lnurl1dp68gurn8ghj7ampd3kx2ar0veekzar0wd5xjtnrdakj7tnhv4kxctttdehhwm30d3h82unvwqhhxarpw3jkc7tzw4ex6cfexyfua2nr  86fA3qPTeQtNb2k1vLwEQaAp3XxkvvvXt69gSG5LGunXXikK9koPWZaRQgfFPBPWhMgXjPjccy9LA9xRFchPWQAnPvxh5Le paypal.me/distrowatchweekly • patreon.com/distrowatch |
|
| Extended Lifecycle Support by TuxCare |
|
|
| Reader Comments • Jump to last comment |
1 • Portable packages (by bison on 2019-09-30 00:48:18 GMT from United States)
I use portable packages for games and music software -- when I can find them -- so that applications don't stop working when I upgrade to a newer distribution with libraries that are not backward compatible. I'm still looking for a AppImage or Flatpak for SuperTuxKart 0.7.3 so that I don't have to boot into an old (and unsupported) version of Ubuntu to play the game.
2 • Refreshed ISO files versus on-line updates (by 6r00k14n on 2019-09-30 01:22:14 GMT from United States)
Having dealt with Debian installs both from an image and from a netinstall disc, I prefer an image, because it will get the system up and running quickly, particularly with a slow connection. You can always run the updates while you are configuring the system.
3 • Refreshed ISO files versus on-line updates (by Titus_Groan on 2019-09-30 02:10:53 GMT from New Zealand)
or, unless the image is really old /stale, use both the image and online together.
That way you get the relatively fast image install, and any updates that available on your nearest mirror.
(oh, that's right, not every Linux distro install support that hybrid option)
4 • Portable apps (by Unaspire on 2019-09-30 05:21:37 GMT from Indonesia)
Voted for 'a combination of the above', but IMHO the only true 'portable' here are either executable binaries built/released from the devs, or AppImages. I do not think it is possible to manually download, install ETC snaps/flatpaks so yeah, IMHO they are not that 'portable'. I have only used them a few times just to see what happens, and do not like them.
Thankfully everything I need usually releases an AppImage on their site. We can also find many more from other sources like bintray, appimagehub and so on.
5 • portable packages (by pin on 2019-09-30 05:35:47 GMT from Sweden)
Don't use them and won't use them. They are system bloat, a security concern and a wrong way of software distribution.
6 • freedombox (by matt on 2019-09-30 06:08:38 GMT from United States)
I first heard about freedombox years ago, I think it was a talk by Eben Moglen. It's great to see how it is developing. It looks pretty polished and easy to use.
7 • tried portable packages (by Dxvid on 2019-09-30 09:45:43 GMT from Sweden)
I have tried portable packages on a couple of Linux distros but have experienced problems with both snap and flatpak in the past. Apart from being unstable using portable packages also takes unnecessary space.
I decided a year ago to take a pause and see if portable packages are more stable in a few years. Maybe I'll try again in a couple of years from now and like it.
I think so far spotify is the only company forcing us to use snap. But I use the web browser instead to avoid snap or run spotify from my phone.
8 • Portable Package Formats (by kc1di on 2019-09-30 10:36:31 GMT from United States)
I've used all three of the major offerings and only one I currently use is Appimage. It works very well for the programs I need and seems to be reliable. And I can use the same image no matter which Distro is being used.
I find Snap and Flatpak inconsistent and bloated most of the time. And not all that portable.
9 • Portable progs (by Roger on 2019-09-30 10:49:44 GMT from Belgium)
I use them mainly so that I have the same progs on different OS, including Win. D'ont use Mac. Portable apps is a nice tool tot have with you, 16 Gb stick and ready.
10 • Portable packages (by Kazlu on 2019-09-30 10:51:08 GMT from France)
My main reason to use portable packages is when I cannot get that package otherwise. Simple as that.
11 • Freedombox (by zcatav on 2019-09-30 10:57:57 GMT from Turkey)
I'm trying out Freedombox testing on Raspberry Pi 3B. And I can't able to run Cockpit. I wonder have you tried ejabberd service?
Thanks for your detailed Freedombox review.
12 • Portable packages (by OstroL on 2019-09-30 12:37:48 GMT from Poland)
All web browsers are portable these days. Everything is included in the folder. What is missing can be pasted to that folder, if one wants. Then, keep that folder anywhere and click on the executive file in it, or have a symlink to it somewhere. I think Libre Office, Gimp and most other apps can be run that way.
13 • Refreshed ISO files versus on-line updates (by Michael on 2019-09-30 12:49:08 GMT from Germany)
@Jesse
I assume you refer to your example with Manjaro updates on the 32-bit version. That is very big indeed. From my point of view, this seems to be the exception, because if I look at the current 64-bit variants, I find at any time current ISO images, which offer only a few updates after the fresh installation.
In general, in this case of the big 32-bit update by the developers, it is also recommended to install the update procedure via tty instead of using a package manager via GUI.
14 • Refreshed ISO files (by dragonmouth on 2019-09-30 13:07:53 GMT from United States)
I agree with Jesse that it is highly impractical for developers to keep the ISO up-to-the-minute. PCLinuxOS which I use gets package updates at least 3 times a week, sometimes every day. The updates are usually small (less than 10 packages) so spending 5 or 10 minutes on applying them is no big deal.
After I do a fresh install of a distro, I fire up my package manager and uninstall any packages that I know I will never use. Then I apply any updates that may be available. I expect the entire process to take 2-3 hours, no matter what. So the size of the initial update is immaterial.
15 • AppImage (by pepa65 on 2019-09-30 13:35:45 GMT from Thailand)
Tried snaps, too resource intensive, all the mounting, it was burdensome. I haven't really gotten the point of flatpaks. But AppImages can be really handy, just a single binary that is supposed to contain all it needs to run. Doesn't clutter up the file system, so especially for packages you don't want to install, or that aren't available, or not in the version I want, but you can just run it. It does require fuse, so on tiny systems they might not work out of the box. I like the simplicity of a single binary, like a go application. And like a go application, you can even build them yourself (see lvml/makeaoi on Github).
16 • this week poll is too general (by artix_user on 2019-09-30 13:42:13 GMT from Moldova, Republic of)
I think that the poll in its current format was useless,
ubuntu article did it more accurately.
You simply cannot ask Arch and Debian users same questions,
cause the answers will be very different.
The power of *nix is that every one can find distributions suited for their needs.
17 • Portable Packages (by Dennis Ajeman on 2019-09-30 13:50:49 GMT from United States)
I am a Kubuntu user (KDE since the mid 90's) and use snaps of Firefox and Chromium as the standard packages have unbridled memory problems that consistantly crash the system forcing a hard reboot. The snap packages are also approximately 3 x's faster than the standard. I use an appimage of Digikam since the repository package has a beard longer than mine.
18 • Updates and such... (by Friar Tux on 2019-09-30 13:55:53 GMT from Canada)
Regarding updates... one of the things I like about updates on Linux is that the USER gets to pick when to install them. I do mine once a week, usually Fridays, then I do my backups. Most of the time they take about half an hour, together. While 'Dumputer' is updating and 'backupping', I'm enjoying a cup of tea. Then we all go to bed.
As for Appimages, Flatpaks, or Snaps, I don't use them. First off, I have found that they are either older versions of the software, or limited versions, with some features locked or missing. Secondly, they seem to be quite large as they contain all the required libraries instead of using the libraries already in the system like their regular versions. This takes up quite a bit of disc/ssd real estate that could be used otherwise. If a particular app/programme only comes in the so called 'portable' format, I simply find an alternative.
19 • @ 17 Really? (by kaczor on 2019-09-30 14:37:54 GMT from Greece)
"The snap packages are also approximately 3 x's faster than the standard."
Really? Don't know what type of grass you've been smoking.
20 • Portable packages (by TheTKS on 2019-09-30 14:38:32 GMT from Canada)
Appimages only, and only one app at the moment. I like that you can use an application without actually installing it, and if you want to get rid of it, delete one file.
I have tried snaps and flatpaks, but I get no advantage from them. There’s a bit of extra work to set up snap & flatpak, and the packages loaded more slowly than the installed packages when I last used these a year+ ago.
If it becomes impossible or a big hassle to avoid using snap or flatpak, then I’ll use them. Ubuntu is already talking about making Chromium available as snap only. I don’t want to compile from source big packages like browsers just to avoid snap or flatpak.
A potential concern that’s been mentioned is security. I don’t know if it’s possible to use portable packages as securely as regular packages. I want to understand that before I would consider using them more.
I’m not concerned about bloat with just a couple of packages (the most I ever installed was 4 snaps, and never ran more than two at the same time.) If you start using a lot of them, maybe it would become a problem.
TKS
21 • FreedomBox (by gplcoder on 2019-09-30 14:46:06 GMT from Austria)
I have a FreedomBox up and running on the ARM hardware that the organization advocates (a no-blob computer). I have configured it with a domain name, a Lets Encrypt cert, Fail2Ban, ejabberd, infinoted (Gobby server), JSXC (Web jabber client), Mumble server and Privoxy. In addition, Cockpit is working (not the white-screen-of-death). Best I can figure, Cockpit worked for me after I configured the domain and added the Lets Encrypt cert. The FreedomBox also likes to be rebooted after the addition of a service (even though the web interface does not mention this). I have had lots of services give me errors only to go away after I rebooted.
Overall, a great distro but it is not as easy/transparent as the documentation says. Network configuration remains quite involved (as usual).
22 • Portable (potty) (by vern on 2019-09-30 14:57:17 GMT from United States)
Flatpaks, or Snaps = Bloat Beyond Belief.
Not sure about Appimages, never used it.
23 • packages on thumb drive (by Otis on 2019-09-30 15:19:43 GMT from United States)
We take them with us instead of our computers when we visit friends/family not near us.
24 • Freedom Box (by Gary on 2019-09-30 15:45:02 GMT from United States)
Had been looking for a Home Server that, as someone not comfortable (yet) with the Command line, I can use with several different Distros at the same time. Since your review of FreedomBox was so good, I'm gonna give it a try. Thanks!!
Also, never used Flat or Snap Paks. After reading the comments here, I think I'll wait for a while before I do.
25 • About portable packages (by JerareYoshi on 2019-09-30 17:14:13 GMT from France)
I use portable packages so i can use theme across differents distros. Also because softwares are apart of the system, we can reinstall easier.
26 • Portable Packages (by dragonmouth on 2019-09-30 18:08:54 GMT from United States)
When using AppImage, Snaps or Flatpak when different packages require different versions of the same library? Do we have the return of DLL Hell?
27 • Portable Packages (by StephenC on 2019-09-30 18:21:38 GMT from United States)
Debian, using AppImages for digikam and stellarium. Also using FireJail to contain them.
Still way better than Windows random shareware binary downloaded with unknown capabilities...
#26, no with AppImages it is self-contained.
Regardless of the app type used (appimage/snap/flat pack/etc...), it should be combined with a container/permissions of some kind to limit damage if you get a rogue copy.
28 • Using a snap package on Ubuntu (by eco2geek on 2019-09-30 18:52:42 GMT from United States)
I've been using a Chromium snap on Ubuntu 19.04/19.10 because that's how Ubuntu packages it these days.
Since snaps are sandboxed, it turned out that if I wanted to be able to download anything to a partition on my hard drive, I had to change the snap's permissions. The easiest way to do this is, after installation, to go to the snap's page in the "Software" application and click the "Permissions" button, and enable "Read/write files on removable storage devices".
The snap doesn't follow the desktop environment's (Yaru) theme, either.
In the future, I'm probably going to just install Google Chrome instead.
29 • Portable Packages (by Martin on 2019-09-30 18:52:43 GMT from United Kingdom)
I have never tried any form of portable packages, I have no need for them and seek to keep my installations as slim as possible.
30 • Portable Packages (by Lupus on 2019-09-30 21:04:54 GMT from Germany)
Time and Development are funny things. Back in the days when I still was a disgruntled windows user I really got into the idea of portable apps. They do great work and I was able to have my working environment on a stick. I hated to search for every damn driver and software update on my own and all over the place. So the site portable apps really hit two birds with one stone. What little did I know of Free and open Source Linux. Once I got the concept of repositories and updating your System in the background without even having to boot several times I was hooked and nowadays my whole family with the exception of the deranged apple bunch uses it too. But low and behold there we are again portable apps for Linux WTF???
I understand there may be usecases but I have to say:" A small step for man.... a giant leap backwards for mankind." If you are an avid Linux user you don´t need that.
Just a thought BTW
31 • snaps (by ed on 2019-09-30 22:42:48 GMT from United States)
Only way I could get Foobar 2000, best music player available imho, was through snap. Hopefully it becomes part of distros someday or in software choices in software managers.
32 • Portable packages (by Romane on 2019-10-01 06:08:21 GMT from Australia)
I selected 'other reason', simply because no other answer aligned with my use case.
I use just one portable package, and that because it is not in the repositories of many distributions, and because the version packaged for Debian (actually, Ubuntu) by the developers won't run on my Debian Testing system.
Did try snap once, so probably not a fair test. But never tried again because it failed to properly install that one package I consider essential to my daily computer usage. Have tried AppImage with fairly good success for other packages. But my format of choice, as I have found it 100% reliable for installing that one package I need is Flatpak.
33 • portable packages (by portab on 2019-10-01 07:46:43 GMT from Norway)
I like to use appimages.
I don't like flatpaks, however would use them if there are no other options.
I run like hell from snaps, will never ever use snaps no matter what.
34 • Chromium Snap2 made me run away from Kubuntu (by Flavio on 2019-10-01 12:04:43 GMT from Brazil)
I have used Kubuntu since April 2009, and lately I was using 19.10 development branch.
But when regular updates automaticly replaced Chromium.deb with Chromium.snap2 ─ and I saw there would be no more option ─ I removed Kubuntu from my desktop forever.
Now, just KDE Neon and Mint 18 KDE, while still possible.
Using mostly Mageia, Fedora, openSUSE, PCLinuxOS ─ all KDE ─ with no portable package.
35 • Portable packages/ snaps (by Barnabyh on 2019-10-01 20:04:28 GMT from Germany)
I'm running only one snap and that is for Chromium, it appears well integrated in LMDE 3 and I had no issues when compared to the previous, older versions supplied in the repo. Snaps also appear to be sandboxed as someone already stated above and on top of that I added and enabled apparmor to this install of LMDE (essentially Debian 9 which does not include apparmor by default yet).
Currently also using Mageia as a stable base for a media centre where PCLOS as a rolling distro is updating way too often for my taste. Chromium there is still on 74 so snaps may be a way forward here too. But I've decided to standardize on Palemoon now. Only issue is carrying over all the saved passwords bit by bit. I've imported them all into a password manager and a protected spreadsheet but still, more painful to look up until they are all saved again into a new browser. So yes, convenience is a big part in staying with the same software, in particular after so many years of using computers. Sometimes it gets tiring reinventing the wheel.
36 • Snaps and why they are slow (by OstroL on 2019-10-02 06:38:10 GMT from Poland)
Ubuntu usually comes default with Gnome Calculator as a snap, and this app/snap starts slowly. It lives in snap/gnome-calculator/406/, bit too far to look for. Now, if you run snap/gnome-calculator/406/usr/bin/gnome-calculator in the terminal, it won't run, for "Settings schema 'org.gnome.calculator' is not installed." ow, install gnome-calculator through sudo apt install gnome-calculator, and the gschema would be installed.
You loo in the Gnome shell app grid, you have 2 calculators. One would start slowly, and the other immediately. The one that start slowly is the snap one.
Now, run snap/gnome-calculator/406/usr/bin/gnome-calculator in the terminal again, the calculator starts immediately. You are running, supposedly, the calculator in the snap, as the path shows.
In Linux, the exe file is in /usr/bin. In the snap too, but to go there, the signal must go to /snap/name folder/numbered folder/usr/bin/, but not to the "normal" /usr/bin. The path is longer, so snap is slow to start.
Check before commenting, please.
37 • snaps (by anticapitalista on 2019-10-02 09:44:08 GMT from Greece)
Just to point out that on Debian and Ubuntu based distros, snaps need systemd.
38 • @37 those fake dependencies again (by curious on 2019-10-02 11:27:29 GMT from Germany)
If snaps only "need" systemd on Debian and Ubuntu based distros, that is an obvious hint that the "need" for systemd is artificial.
To me, that kind of fake dependency is EVIL - and these fake dependencies that "require" the use of systemd even for software that shouldn't have anything to do with the init system are my main criticism about the way systemd was introduced, since they take away choice - not only from the users, but also from distro creators, for whom they make choosing any other init system than systemd much more difficult.
It looks as if some people are very afraid that systemd would not be adopted on the basis of technical (or any other) merits alone ...
39 • Snaps and Ubuntu (by kaczor on 2019-10-02 11:41:25 GMT from Greece)
Snaps are for IoT, which is what Cannonical is trying to move in, or already moved in to. Cannonical has no interest in the desktop, for it had become just a problem for it, not bringing in profit. Ubuntu is atm in the hands of amateurs, so called community, and without any real directions from the Cannonical owner.
Snaps in the desktop Ubuntu runs slowly. The same apps installed in the deb format runs faster. No other distro would touch snaps. Even, Linux Mint, offshoot of Ubuntu favours flatpaks.
40 • impossible to create an embedded environment with Debain and Systemd (by Mikael Palmkvist on 2019-10-02 14:44:39 GMT from Sweden)
You got very bad realtime performance using systemd if you ad t.ex. realtime platform in bottom using RTAI or other real realtime operative systems, then Linux itself become useless.
You just insteall the Realtime OS and skip Linux for all none realtime solutions above.
It complicate too much also on Servers there systemd is worthless.
It is sad that systemd is not an option as it is no a requirement to use debain.
I have to skip the Linux when I develope embedded software today.
41 • New Package Formats (by Thomas Taylor on 2019-10-02 15:00:20 GMT from United States)
I wish they would figure out the best and go with it.
This is one area they shouldn't keep a bunch of different ones going.
That way when they get all packages converted.
We might see a package based Distro.
42 • extraneous package formats (by Ed Ktorp on 2019-10-03 22:57:19 GMT from United States)
Snaps, Flatpaks.. what's the difference? This is just the latest faux-choice to grease the skids for systemd/linux to end up with a 'universal' method of package management, even though (as was pointed out by #38) there is no technical reason why these 'portable' formats should require systemd. But they will.
43 • package missing library (by Li Huang on 2019-10-04 07:18:39 GMT from United States)
I never had any problem with slap packages. In GapImagination, I always fall flat.
But, never had any problems so far.
I do have different problem here:
I am trying swfdec working properly,
but it says liboil 0.3.17-3 is missing.
My name is Li, and as it says li->boil 0.3.17-3,
I already boiled 3 eggs sharp at 3.17,
but swfdec still syas liboil is missing.
I also put few deops of librizol's oil.
but swfdec still syas liboil library is missing.
Unfortunately, i do not have enough space to accommodate whole library.
Before I say-wf-decently to swfdec,
Please, Can anyone help me out here?
for what's going on.
Number of Comments: 43
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 1129 (2025-07-07): GLF OS Omnislash, the worst Linux distro, Alpine introduces Wayback, Fedora drops plans to stop i686 support, AlmaLinux builds EPEL repository for older CPUs, Ubuntu dropping existing RISC-V device support, Rhino partners with UBports, PCLinuxOS recovering from website outage |
| • Issue 1128 (2025-06-30): AxOS 25.06, AlmaLinux OS 10.0, transferring Flaptak bundles to off-line computers, Ubuntu to boost Intel graphics performance, Fedora considers dropping i686 packages, SDesk switches from SELinux to AppArmor |
| • Issue 1127 (2025-06-23): LastOSLinux 2025-05-25, most unique Linux distro, Haiku stabilises, KDE publishes Plasma 6.4, Arch splits Plasma packages, Slackware infrastructure migrating |
| • Issue 1126 (2025-06-16): SDesk 2025.05.06, renewed interest in Ubuntu Touch, a BASIC device running NetBSD, Ubuntu dropping X11 GNOME session, GNOME increases dependency on systemd, Google holding back Pixel source code, Nitrux changing its desktop, EFF turns 35 |
| • Issue 1125 (2025-06-09): RHEL 10, distributions likely to survive a decade, Murena partners with more hardware makers, GNOME tests its own distro on real hardware, Redox ports GTK and X11, Mint provides fingerprint authentication |
| • Issue 1124 (2025-06-02): Picking up a Pico, tips for protecting privacy, Rhino tests Plasma desktop, Arch installer supports snapshots, new features from UBports, Ubuntu tests monthly snapshots |
| • Issue 1123 (2025-05-26): CRUX 3.8, preventing a laptop from sleeping, FreeBSD improves laptop support, Fedora confirms GNOME X11 session being dropped, HardenedBSD introduces Rust in userland build, KDE developing a virtual machine manager |
| • Issue 1122 (2025-05-19): GoboLinux 017.01, RHEL 10.0 and Debian 12 updates, openSUSE retires YaST, running X11 apps on Wayland |
| • Issue 1121 (2025-05-12): Bluefin 41, custom file manager actions, openSUSE joins End of 10 while dropping Deepin desktop, Fedora offers tips for building atomic distros, Ubuntu considers replacing sudo with sudo-rs |
| • Issue 1120 (2025-05-05): CachyOS 250330, what it means when a distro breaks, Kali updates repository key, Trinity receives an update, UBports tests directory encryption, Gentoo faces losing key infrastructure |
| • Issue 1119 (2025-04-28): Ubuntu MATE 25.04, what is missing from Linux, CachyOS ships OCCT, Debian enters soft freeze, Fedora discusses removing X11 session from GNOME, Murena plans business services, NetBSD on a Wii |
| • Issue 1118 (2025-04-21): Fedora 42, strange characters in Vim, Nitrux introduces new package tools, Fedora extends reproducibility efforts, PINE64 updates multiple devices running Debian |
| • Issue 1117 (2025-04-14): Shebang 25.0, EndeavourOS 2025.03.19, running applications from other distros on the desktop, Debian gets APT upgrade, Mint introduces OEM options for LMDE, postmarketOS packages GNOME 48 and COSMIC, Redox testing USB support |
| • Issue 1116 (2025-04-07): The Sense HAT, Android and mobile operating systems, FreeBSD improves on laptops, openSUSE publishes many new updates, Fedora appoints new Project Leader, UBports testing VoLTE |
| • Issue 1115 (2025-03-31): GrapheneOS 2025, the rise of portable package formats, MidnightBSD and openSUSE experiment with new package management features, Plank dock reborn, key infrastructure projects lose funding, postmarketOS to focus on reliability |
| • Issue 1114 (2025-03-24): Bazzite 41, checking which processes are writing to disk, Rocky unveils new Hardened branch, GNOME 48 released, generating images for the Raspberry Pi |
| • Issue 1113 (2025-03-17): MocaccinoOS 1.8.1, how to contribute to open source, Murena extends on-line installer, Garuda tests COSMIC edition, Ubuntu to replace coreutils with Rust alternatives, Chimera Linux drops RISC-V builds |
| • Issue 1112 (2025-03-10): Solus 4.7, distros which work with Secure Boot, UBports publishes bug fix, postmarketOS considers a new name, Debian running on Android |
| • Issue 1111 (2025-03-03): Orbitiny 0.01, the effect of Ubuntu Core Desktop, Gentoo offers disk images, elementary OS invites feature ideas, FreeBSD starts PinePhone Pro port, Mint warns of upcoming Firefox issue |
| • Issue 1110 (2025-02-24): iodeOS 6.0, learning to program, Arch retiring old repositories, openSUSE makes progress on reproducible builds, Fedora is getting more serious about open hardware, Tails changes its install instructions to offer better privacy, Murena's de-Googled tablet goes on sale |
| • Issue 1109 (2025-02-17): Rhino Linux 2025.1, MX Linux 23.5 with Xfce 4.20, replacing X.Org tools with Wayland tools, GhostBSD moving its base to FreeBSD -RELEASE, Redox stabilizes its ABI, UBports testing 24.04, Asahi changing its leadership, OBS in dispute with Fedora |
| • Issue 1108 (2025-02-10): Serpent OS 0.24.6, Aurora, sharing swap between distros, Peppermint tries Void base, GTK removinglegacy technologies, Red Hat plans more AI tools for Fedora, TrueNAS merges its editions |
| • Issue 1107 (2025-02-03): siduction 2024.1.0, timing tasks, Lomiri ported to postmarketOS, Alpine joins Open Collective, a new desktop for Linux called Orbitiny |
| • Issue 1106 (2025-01-27): Adelie Linux 1.0 Beta 6, Pop!_OS 24.04 Alpha 5, detecting whether a process is inside a virtual machine, drawing graphics to NetBSD terminal, Nix ported to FreeBSD, GhostBSD hosting desktop conference |
| • Issue 1105 (2025-01-20): CentOS 10 Stream, old Flatpak bundles in software centres, Haiku ports Iceweasel, Oracle shows off debugging tools, rsync vulnerability patched |
| • Issue 1104 (2025-01-13): DAT Linux 2.0, Silly things to do with a minimal computer, Budgie prepares Wayland only releases, SteamOS coming to third-party devices, Murena upgrades its base |
| • Issue 1103 (2025-01-06): elementary OS 8.0, filtering ads with Pi-hole, Debian testing its installer, Pop!_OS faces delays, Ubuntu Studio upgrades not working, Absolute discontinued |
| • Issue 1102 (2024-12-23): Best distros of 2024, changing a process name, Fedora to expand Btrfs support and releases Asahi Remix 41, openSUSE patches out security sandbox and donations from Bottles while ending support for Leap 15.5 |
| • Issue 1101 (2024-12-16): GhostBSD 24.10.1, sending attachments from the command line, openSUSE shows off GPU assignment tool, UBports publishes security update, Murena launches its first tablet, Xfce 4.20 released |
| • Issue 1100 (2024-12-09): Oreon 9.3, differences in speed, IPFire's new appliance, Fedora Asahi Remix gets new video drivers, openSUSE Leap Micro updated, Redox OS running Redox OS |
| • Issue 1099 (2024-12-02): AnduinOS 1.0.1, measuring RAM usage, SUSE continues rebranding efforts, UBports prepares for next major version, Murena offering non-NFC phone |
| • Issue 1098 (2024-11-25): Linux Lite 7.2, backing up specific folders, Murena and Fairphone partner in fair trade deal, Arch installer gets new text interface, Ubuntu security tool patched |
| • Issue 1097 (2024-11-18): Chimera Linux vs Chimera OS, choosing between AlmaLinux and Debian, Fedora elevates KDE spin to an edition, Fedora previews new installer, KDE testing its own distro, Qubes-style isolation coming to FreeBSD |
| • Issue 1096 (2024-11-11): Bazzite 40, Playtron OS Alpha 1, Tucana Linux 3.1, detecting Screen sessions, Redox imports COSMIC software centre, FreeBSD booting on the PinePhone Pro, LXQt supports Wayland window managers |
| • Issue 1095 (2024-11-04): Fedora 41 Kinoite, transferring applications between computers, openSUSE Tumbleweed receives multiple upgrades, Ubuntu testing compiler optimizations, Mint partners with Framework |
| • Issue 1094 (2024-10-28): DebLight OS 1, backing up crontab, AlmaLinux introduces Litten branch, openSUSE unveils refreshed look, Ubuntu turns 20
| | • Issue 1093 (2024-10-21): Kubuntu 24.10, atomic vs immutable distributions, Debian upgrading Perl packages, UBports adding VoLTE support, Android to gain native GNU/Linux application support |
| • Issue 1092 (2024-10-14): FunOS 24.04.1, a home directory inside a file, work starts of openSUSE Leap 16.0, improvements in Haiku, KDE neon upgrades its base |
| • Issue 1091 (2024-10-07): Redox OS 0.9.0, Unified package management vs universal package formats, Redox begins RISC-V port, Mint polishes interface, Qubes certifies new laptop |
| • Issue 1090 (2024-09-30): Rhino Linux 2024.2, commercial distros with alternative desktops, Valve seeks to improve Wayland performance, HardenedBSD parterns with Protectli, Tails merges with Tor Project, Quantum Leap partners with the FreeBSD Foundation |
| • Issue 1089 (2024-09-23): Expirion 6.0, openKylin 2.0, managing configuration files, the future of Linux development, fixing bugs in Haiku, Slackware packages dracut |
| • Issue 1088 (2024-09-16): PorteuX 1.6, migrating from Windows 10 to which Linux distro, making NetBSD immutable, AlmaLinux offers hardware certification, Mint updates old APT tools |
| • Issue 1087 (2024-09-09): COSMIC desktop, running cron jobs at variable times, UBports highlights new apps, HardenedBSD offers work around for FreeBSD change, Debian considers how to cull old packages, systemd ported to musl |
| • Issue 1086 (2024-09-02): Vanilla OS 2, command line tips for simple tasks, FreeBSD receives investment from STF, openSUSE Tumbleweed update can break network connections, Debian refreshes media |
| • Issue 1085 (2024-08-26): Nobara 40, OpenMandriva 24.07 "ROME", distros which include source code, FreeBSD publishes quarterly report, Microsoft updates breaks Linux in dual-boot environments |
| • Issue 1084 (2024-08-19): Liya 2.0, dual boot with encryption, Haiku introduces performance improvements, Gentoo dropping IA-64, Redcore merges major upgrade |
| • Issue 1083 (2024-08-12): TrueNAS 24.04.2 "SCALE", Linux distros for smartphones, Redox OS introduces web server, PipeWire exposes battery drain on Linux, Canonical updates kernel version policy |
| • Issue 1082 (2024-08-05): Linux Mint 22, taking snapshots of UFS on FreeBSD, openSUSE updates Tumbleweed and Aeon, Debian creates Tiny QA Tasks, Manjaro testing immutable images |
| • Issue 1081 (2024-07-29): SysLinuxOS 12.4, OpenBSD gain hardware acceleration, Slackware changes kernel naming, Mint publishes upgrade instructions |
| • Issue 1080 (2024-07-22): Running GNU/Linux on Android with Andronix, protecting network services, Solus dropping AppArmor and Snap, openSUSE Aeon Desktop gaining full disk encryption, SUSE asks openSUSE to change its branding |
| • Issue 1079 (2024-07-15): Ubuntu Core 24, hiding files on Linux, Fedora dropping X11 packages on Workstation, Red Hat phasing out GRUB, new OpenSSH vulnerability, FreeBSD speeds up release cycle, UBports testing new first-run wizard |
| • Issue 1078 (2024-07-08): Changing init software, server machines running desktop environments, OpenSSH vulnerability patched, Peppermint launches new edition, HardenedBSD updates ports |
| • Issue 1077 (2024-07-01): The Unity and Lomiri interfaces, different distros for different tasks, Ubuntu plans to run Wayland on NVIDIA cards, openSUSE updates Leap Micro, Debian releases refreshed media, UBports gaining contact synchronisation, FreeDOS celebrates its 30th anniversary |
| • 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 | 
Qomo Linux
Qomo Linux (formerly Everest Linux) was a Chinese distribution developed by Red Flag Linux and managed as a community project (in a fashion similar to Red Hat's Fedora or Novell's openSUSE). Its main features are user-friendly desktop, excellent hardware detection, full support for simplified Chinese, and a 6-month release cycle.
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.
|
|
• 
• 
• 
• 
• 
• 
• 
