| DistroWatch Weekly
|DistroWatch Weekly, Issue 373, 27 September 2010
Welcome to this year's 39th issue of DistroWatch Weekly! The demise of OpenSolaris, following the project's acquisition by Oracle, has brought both anger and action from its developer community. As a result, OpenIndiana, a community fork of OpenSolaris, was born. The first development release hit the download mirrors early last week and Jesse Smith was quick to take it for a spin. How does it fare compared to desktop Linux or BSD? Read on to find out. In the news section, Fedora continues its march towards the next stable version with a public beta release, Ubuntu's "Maverick" version brings new questions about the suitability of 6-month release cycles, Mandriva reassures its user community that it will continue developing a free distribution, and PCLinuxOS and its founder get exposure in a mainstream tech publication. Also in this issue, a question and answer section that responds to those users who feel frustrated with the current state of desktop Linux. Happy reading!
Listen to the Podcast edition of this week's DistroWatch Weekly in OGG (18MB) and MP3 (21MB) formats
Join us at irc.freenode.net #distrowatch
|Feature Story (by Jesse Smith)
Solaris holds a special place in my heart. It was my first taste of UNIX, back in my school days, and I probably wouldn't have become involved with the Linux community if I hadn't been searching for a free version of "this UNIX thing" so I could practise my shell scripting at home. I was thrilled when Sun announced they were releasing OpenSolaris for the community to play with, even if it was several years too late to help me with my homework. And I was very disappointed when Oracle executed OpenSolaris earlier this year. Fortunately for Solaris fans the OpenIndiana project is picking up where Sun left off. I had been itching to try a new version of OpenSolaris since February (when the last release was scheduled) and so I quickly grabbed the newly launched OpenIndiana, development build 147.
Installation and hardware support
Before diving into the contents of the DVD, first let me say that the project's web site is very much a work in progress. Many pages haven't been posted yet and the site is mostly an introduction to the project and a download page. No doubt these will be filled in later, but for now the web site is mostly bare. What we can learn in those few pages is that OpenIndiana is working with the Illumos project to make a binary compatible fork of OpenSolaris. Or what used to be OpenSolaris. Maintaining binary compatibility will allow people to freely test their systems and software with OpenIndiana prior to trying an official Solaris product.
The installation CD is an 870 MB download, which I burned to a DVD. The DVD kicks off with a GRUB (legacy) boot menu which allows the user to boot into the live environment, boot using the vesa driver or boot into a text console. The menu additionally has options for running a screen reader or magnifier. After an option has been selected, the system asks for the user's keyboard layout and preferred language. We then get a quick shot of a login screen followed by another prompt asking for our preferred language. We finally arrive at a beautiful blue-themed GNOME 2.30 desktop. The application menu, quick-launch bar and clock are at the top of the screen and the task switcher is placed at the bottom. On the desktop we find icons for the Device Driver Utility, a partition editor, the installer and Firefox. I feel the Device Driver program deserves a special mention.
When we first boot into the OpenIndiana desktop the system will check the status of our hardware drivers and, if there are any problems, will display a discreet warning in the corner of the screen. Opening the Device Driver Utility will show a nice itemized list of the hardware on our system with appropriate icons. Devices for which the operating system does not have corresponding drivers will be highlighted in a reddish-pink colour. Should we have, or know the location of, an appropriate driver package we can give its location in this window and OpenIndiana will install it. This process is so convenient, straightforward and user-friendly I think it should be a standard feature in all FOSS operating systems. It completely removes the guess work and testing phases of discovering whether the OS will run on a machine.
For instance, on my desktop machine, the utility found a (largely unused) modem for which it didn't have a driver. Everything else on the desktop (2.5 GHz CPU, 2 GB of RAM, NVIDIA video card) worked. My HP laptop (dual-core 2 GHz CPU, 3 GB of RAM, Intel video card) was also handled well. However, the utility let me know that my Intel wireless card wasn't supported. Most other things such as resolution, sound and networking worked without any trouble. My touchpad handled taps as clicks, but wouldn't scroll under the default settings -- a reverse from the normal order of things. The user has the option of using the utility to submit their hardware profile, similar to the way Fedora's Smolt does on Linux machines. I sent a profile for my desktop machine and found it interesting that the utility says the hardware information was sent to Sun. This seems out of date at best and I wonder who ended up with a list of my hardware.
Next up is the system installer. The first thing the user is asked to do is handle partitions. Compared to other graphical installers (and a few text-based installers) the OpenIndiana partitioner is a bit sparse and I found it easier to divide up the disk using GParted prior to running the installer. Next the user is asked for their time zone and preferred language. (This was the third time I'd selected my language preference since booting.) The following screen creates a user account, which we are told will have administrator privileges. The installer then copies over the required files and we reboot.
OpenIndiana dev-146 - administration tools
(full image size: 625kB, resolution 1280x1024 pixels)
First impressions and software applications
OpenIndiana does not boot quickly. The first time I started the system post-install, the system took about five minutes to reach the login screen. Later start-up times were improved, but still dragged compared to most Linux distros. After logging in, I found the installed system was much the same as the live DVD environment, though without desktop icons. A little poking around showed the system (once up and running) wasn't so much slow as heavy. Running on a physical machine with 2 GB of RAM, OpenIndiana did fairly well; however, trying to cram the OS into a virtual machine with 1 GB of memory caused a noticeable drop in responsiveness. I think a good deal of the overhead comes from the ZFS file system which is nicely integrated into the system. OpenIndiana has some slick GUI tools for dealing with ZFS and the file browser has a built-in "time slider" that allows quick access to file system snapshots. When using OpenSolaris last year I had stability issues with the snapshots feature, but I encountered no problems this time around.
The application menu is light for an operating system which comes on a DVD. Included are Firefox (3.6.8), Thunderbird, Pidgin, Rhythmbox, Totem for playing videos, GParted and Java. We also find the usual collection of applications, including a text editor, file archiver, CD ripper, disc burner, a document viewer and accessibility programs. Not to be found on the system are popular media codecs and Flash. Instead, when the user tries to open a media file, a codec helper pops up and offers to help the user purchase the required codec. The prices strike me as being a bit high and, for most regions of the world, unnecessary.
There were a few surprises regarding what was not available on the menu. OpenIndiana is a branch of OpenSolaris, which was managed by Sun Microsystems. I expected the OS would be used as a platform to show off other (former) Sun technologies. For instance there was no OpenOffice.org to be found on the menu, nor in the package manager. Java was pre-installed, but not the associated developer tools. Likewise, I didn't find a copy of VirtualBox. In fact when running in VirtualBox, OpenIndiana doesn't integrate with the host operating system the way some modern Linux distros do. I think it's a shame that more work hasn't been done to incorporate these projects into the platform. I think Sun, and Oracle, lost an opportunity there to show what they could achieve.
OpenIndiana dev-146 - searching for packages
(full image size: 717kB, resolution 1280x1024 pixels)
That's not to say there aren't some good tools which come with OpenIndiana. There are applications with nice interfaces for handling core files, services, the firewall, users and packages. For the most part, these tools are about what a user could expect to find on a Linux or desktop BSD system. I like their layout and I found them intuitive to use. The package manager especially mimics Synaptic both in appearance and behaviour. At the moment the project's repository is a bit light with just over 2,000 packages available. Hopefully that will grow as OpenIndiana matures. One item that stood out was the ZFS snapshot manager. It provides a nice interface for setting up what is included in a snapshot and when snapshots take place.
System administration and security
The thorn in my side as far as OpenIndiana was concerned was in relation to security, specifically root-level access. The system installer mentions that the user account created at install time will have root access. This does not appear to be the case as any admin-type action I tried to preform was met with a request for the root user's password. The first time I saw this and my password was rejected I realized no password had been set for root during the setup process. I created a root password and went back to change settings. At which point I found the root password was rejected as my user did not have permission to elevate my privileges to the root level. Next I went into the user account manager and changed my user's roles to include elevating my access to root-user level. And I realized I had just performed these account changes with my regular user account!
Going down through the menu of administration tools I found that about half would let me use them and change settings with the root password and the other half would deny me access saying my user account was not permitted to act as root, even with the root password. I'm sure there is some role I can change somewhere to make my account be able to effectively su in all cases, but it is a pain to have this kind of inconsistency. Why would security be configured in such a way that by default I can easily manage system packages and accounts, but not be able to change settings for core file dumps and system services? Speaking of services, as one might expect from an operating system which has its ancestry in servers, the OS runs secure shell and Sendmail by default. Under the default settings root is unable to remotely login to a shell.
OpenIndiana dev-146 - managing system processes
(full image size: 508kB, resolution 1280x1024 pixels)
Perhaps it's not fair to make a judgement call so early given that this is OpenIndiana's first release and they're just getting started, but this initial offering felt more like an early beta than a final release. The system is stable and there are some good features in place. I liked the installer and the Device Driver Utility is a great point in the operating system's favour. Hardware support was a little better this time around than it was a year ago on OpenSolaris. But the heavy nature of the operating system combined with the fickle privilege escalation and small package repository makes OpenIndiana an unappealing choice right now for a desktop system. Hopefully these matters will get ironed out as the project matures.
There is one other thing I feel should be addressed. OpenIndiana seems to be lacking a focus. It has its roots in server technology, but it has become memory hungry, runs a desktop and uses a graphical installer. On the other hand it lacks the range of applications and drivers one might expect in a desktop system. Some people have told me it's more of a testing ground for people migrating, testing and developing across platforms, but if that's the case where are the great development tools and virtualization software?
The wonderful tools which were previously attracting people to OpenSolaris (ZFS, DTrace) have been ported to other operating systems. OpenIndiana doesn't showcase Sun/Oracle technology; all it really does is give people an open source version of Solaris. And, if you're into tweaking operating systems or you're considering a migration to Oracle solutions, then I suppose that's all OpenIndiana needs to be. As a former fan of Solaris, I was hoping to find something which stood out, something the operating system could hang its hat on, and I didn't find that. OpenIndiana isn't a bad system by any means, but I haven't found a reason, besides curiosity, to run it either.
|Miscellaneous News (by Ladislav Bodnar)
Fedora prepares for beta release, Mandriva reasserts its continuity, Ubuntu and 6-month release cycles, PCLinuxOS - past and present
Along with the final release of GNOME 2.32, this week will also see the delivery the last public development builds of Fedora 14 (beta) and Ubuntu 10.10 (release candidate) - the two most popular GNOME-centric distributions. For Ubuntu, this will be a near-final build, with just a minimum number of release-critical bug fixes expected to take place between now and the final release on October 10th. For Fedora, things are progressing in a slightly more leisurely manner as the project's next stable version is not expected until early in November. That said, the list of accepted features in Fedora 14 is now nearly completed. Some of the more interesting upgrades include Perl 5.12 and Python 2.7, while the KDE desktop has been brought up to version 4.5 and the NetBeans development environment is at version 6.9. Overall, it doesn't look like the new Fedora release is brimming with many cutting-edge features, but maybe that's a good thing - a little slowdown in the ever-evolving world of a Linux distro's development can't be a bad thing. Besides, it's entirely possible that many Red Hat developers are currently focusing their attention on the upcoming release of Red Hat Enterprise Linux 6, but as soon as that's out of the way, expect Fedora development to pick up strongly once again.
Fedora 14 beta comes with new artwork and desktop theme.
(full image size: 1,551kB, resolution 1280x1024 pixels)
* * * * *
Ubuntu's development cycle will culminate in two weeks when the project's "Maverick Meerkat" release is scheduled to hit the download mirrors around the world. Although this fast development rhythm has been the distribution's feature for several years, there are those, like ITWire's Sam Varghese, who question the reasoning behind such frequent release plans: "Over the last week, I've been playing around with the beta of the forthcoming Ubuntu release - 'Maverick Meerkat' or version 10.10 - which is scheduled to be officially unveiled on October 10. And I have just one question to ask: why is it being released at all? What major changes are present to justify an upgrade? If all that the new version has to show is incremental changes in version numbers of major applications, why is there the need for so much hoo-haa? Is Canonical, the company behind Ubuntu, guilty of becoming a prisoner of its own hype, and unable to revert to some kind of commonsensical schedule that would reflect the correct state of affairs?" The author answers his own question: "We don't need the staged releases, we don't need to be given the impression that a great deal is happening when someone is basically running on the same spot. GNU/Linux has never resorted to hype to propagate itself - good software that does what it promises to do, never goes out of style. A yearly release is something that I could live with."
* * * * *
Mandriva is fighting back. Following a series of bad publicity reports about the state of the company's finances, employee lay-offs, and a new fork founded by well-known former Mandriva developers (Mageia), the company has published an announcement on its official blog. The article, written by current CEO Arnaud Laprévote, insists that Mandriva (the company) is alive and well and that Mandriva Linux (the distribution) is certainly not about to be discontinued: "The next version of the Mandriva community distribution will be available in the first quarter of 2011. The community version of the Mandriva distribution is the one on which the Powerpack distribution, the Corporate Desktop distribution and the Mandriva Enterprise Server distribution are based upon. From a desktop point of view, Mandriva intends to be the best KDE distribution in the world: easy-to-use, stable, rich-featured and with excellent localization. Even if the community distribution will be KDE-focused, we will encourage the community to build GNOME, LXDE, Xfce, E17, etc. editions as value options. The infrastructure to help the community to do that will be put in place." In related news, Per Øyvind (one of the developers still in Mandriva's services) writes that rumours about Mandriva's demise have been greatly exaggerated, while an official press release, published by Vanessa Wall, provides minutes from Mandriva's annual general meeting which took place on September 17th, 2010.
* * * * *
Those Mandriva users who are still perturbed by the continued uncertainty surrounding their favourite distribution might consider another option (besides Mageia) - PCLinuxOS. Although the project hasn't been making many headlines recently, the developers continue to work quietly on the distribution. ITPro's Richard Hillesley reports in PCLinuxOS - Rolling on a river: "The inspiration behind PCLinuxOS, also known as PCLOS, is Bill Reynolds, who is known to fans of PCLinuxOS as Texstar. PCLinuxOS began as an offshoot of Mandrake/Mandriva, to which Texstar had been a long time contributor of third-party packages. The objective was to build a fast, reliable distribution of Linux, that was both a Live distribution on the model of Knoppix and a fully installable and flexible Linux desktop, driven by Reynolds' passion to make the perfect software package. 'I love to package,' he explained. 'It is like a puzzle where all the pieces have to fit together or the code doesn't work. That is my favourite part of doing PCLOS.'" The 4-page article investigates the history of PCLinuxOS before concluding that "PCLinuxOS exists unapologetically to satisfy the demands of its own community, but in doing so reaches a much larger audience. As Reynolds sees it: 'We're just enjoying Linux technology and sharing it with friends who might like it too. We hope you have enjoyed the ride as well.'"
|Questions and Answers (by Jesse Smith)
Frustrated-with-the-state-of-Linux asks: What are Linux distros doing right? I'm saying, nothing is ever solved, nothing moves to a usable state (I fear accessing my NTFS drives, who knows if Samba, FUSE, etc. are actually in working order). There is no information centralized that is actually relevant, only information that is out of date. (I've learnt to never ask anything on a forum, even after "googling", but to re-install instead.) Are there actual "eyes on the code"? Or just a cycle of buggy alphas and orphaned packages? Who's putting out these 101 distros and what kind of back-ends are they building into them to steal data or track users? Linux seems worse and worse the more I learn about... Any thoughts on these points?
DistroWatch answers: Before I get into the point-by-point questions, I want to address the over-all sense of disappointment in this e-mail. When people are first introduced to Linux it's easy to have high expectations. A lot of people in the GNU/Linux community are all too happy to declare the virtues of their favourite operating system while ignoring flaws. As a result, I think a lot of people enter into the Linux community with the thoughts that Linux systems don't have to protect against malware, that the systems are 100% reliable, that open source is a large, friendly commune full of people perfecting each other's code and helping everyone. The unfortunate truth is that there is no perfect operating system, no perfect development model and all communities are made up of individuals. And, for that matter, all operating system environments are made up of individual components.
The reason I bring this up is that the questions presented here sound to me like they're painting the entire GNU/Linux community with the same brush. I think that's not an entirely fair way of looking at things. There are millions of Linux users in the world and, as with any large group, one shouldn't judge the herd by the actions of a segment. For every handful of projects that never become stable there are some which mature and become rock-solid and useful. For all the poorly maintained manual pages, there are a few which are kept current. Certainly there are projects where little or no code review is done, but some projects take code quality and security seriously. And this is generally true across operating systems. Spend enough time observing any large OS community and you'll find a mix of precious gems and mediocre mud.
The overall tone of the questions indicates to me that there is a concern with quality and stability. So I would recommend examining some of the Linux distros which focus on those areas. Debian GNU/Linux, CentOS and Slackware Linux come to mind as platforms which have been around for a long time and have well-deserved reputations for quality. You might also consider looking at the BSDs, which tend to focus on security and stability rather than pushing new features. There may be more of a learning curve with BSDs, but they're solid systems.
On to the individual questions. What are Linux distros doing right? The big name distros are creating solid, polished operating systems that many people can use on their main computer system on a day-to-day basis. Sure there are dozens of small projects that appear and disappear with the seasons, but there are some really great distributions available. There's a good list of quality systems here on DistroWatch. Technologies such as Samba, FUSE and NTFS drivers have been stable for years now. I use them almost on a daily basis and have, for quite some time, without any problems. However, as with any storage technology on any operating system it's a good idea to keep regular backups.
Forums really aren't all that different from everyday life. I find that people often respond in the same way they're approached. So be nice when asking questions on forums. It doesn't always work, on forums as with physical interactions, some people will be rude. Ignore them and focus on the people who do have the desire to help. Also, are there eyes on the code? Most of the core projects have occasional review. The smaller, lesser-known projects often do not. There's no hard and fast rule about peer review. The key difference between open and closed source is that people have the option to examine open source code. Whether that option is used varies with the project.
If you're worried about who is making the hundreds of minor Linux distributions floating around the net, don't use them. Pick a well-known operating system with a good reputation. Developers can put anything they want into their products, so do a little research before you download. Again, the DistroWatch's Top Ten page is a good place to start.
|Released Last Week
Andrew Gillis has announced the release of VortexBox 1.5, a Fedora-based Linux distribution that can turn an unused computer into an easy-to-use music server or jukebox: "We are pleased to announce the release of VortexBox 1.5. As always our goal it to make VortexBox work with any media player. The recent release of iTunes 10 does not work with the old VortexBox DAAP server. We took this opportunity to replace the DAAP server in VortexBox with a better one. The new DAAP server not only works with iTuens 10 but it can server FLAC files to iTunes by encoding them as WAV files inline. This reduces the need to keep a mirror of your music files in MP3 format. We also updated the latest Squeezebox server and added a control panel to control the services on VortexBox. Thanks to everybody who helped with features and bug fixes for this release." Here is the brief release announcement.
VectorLinux 6.0 "SOHO Deluxe"
Robert Lange has announced the release of VectorLinux 6.0 "SOHO DELUXE", a commercial edition with KDE 4.5.0 as the default desktop, out-of-the-box multimedia support, and extra application on the second CD: "The VectorLinux development team is proud to announce the release of VectorLinux 6.0 SOHO Deluxe. This release is based on the KDE 4.5.0 Plasma desktop and latest Xfce as a secondary desktop. Updates from the public release include Digikam 1.4.0, GIMP 2.6.10, K3b 2.0, Scribus, OpenOffice.org, Amarok 2.3.1, KMyMoney, GnuCash and additional games and system updates. Kernel version is 184.108.40.206 which adds new wireless network possibilities. There have been speed and stability improvements. The GUI installer has seen further refinements and is the default installer." Read the rest of the release announcement for more information.
Barry Kauler has announced the release of Quirky 1.3, a small desktop distribution similar to Puppy Linux, but built with a different toolset: "Quirky 1.3 released. This is built from the 'forked' Woof that I have been discussing recently, and is an opportunity to evaluate the changes in Puppy files and streamlined searching in the 'init' script. A small amount of package upgrading since 1.2, but mostly this release is a test bed for the advances in Woof. In particular, 1.3 is built with the 'simplified file names'. Apart from simplified names, there is also an id-string appended to the files, plus streamlining of the search-code in the 'init' script. 'Rerwin' has also made many advances in analog and 3G modem detection, configuration and usage, that are in Woof. Build 1.3 is for us to thoroughly test these new ideas." See the release announcement and release notes for further details.
ArchBang Linux 2010.09
Willensky Aristide has announced the release of ArchBang Linux 2010.09, a variant of Arch Linux featuring Openbox as the default window manager and a selection of lightweight applications: "ArchBang Linux 2010.09 'RELOADED' is out. It's entitled 'RELOADED' because we went back to our original combination (ArchBang = Arch Linux + Openbox). The 64-bit edition is the only one available at this time but by the end of the week the 32-bit edition should be available as well. Changes: no more LXDE; removed xdg-menu for dmenu (dynamic menu); Thunar is back and PCMan File Manager is out; new theme; just VLC for your media needs (removed Exaile and GNOME MPlayer); added GIMP; Xfburn instead of Graveman; Gnumeric added; Evince instead of Xpdf; places pipe-menu; Linux kernel version 220.127.116.11." Visit the project's home page to read the release announcement.
Chakra GNU/Linux 0.2.2
ArchBang Linux 2010.09 - an interesting variant of Arch Linux with Openbox
(full image size: 1,171kB, resolution 1280x1024 pixels)
Phil Miller has announced the release of Chakra GNU/Linux 0.2.2, an Arch-based distribution and live CD featuring the KDE desktop: "We did it! Now with our new page layout and CCR open for public we also have 0.2.2 ready - our second point release of 'Jaz'. This time tribe got a rework to fix bugs we found during last week. We improved CInstall to handle packages and bundles better. Packer will build packages from our community repository now. Your all welcome to add your packages there - we might add them to our binary repositories. Some users reported some issues with VLC and MPlayer. Those are gone now. NVIDIA and ATI drivers got updated and hardware-detection-scripts will find them properly now." Read the rest of the release announcement for more details.
Clonezilla Live 1.2.6-24
Steven Shiau has announced the availability of a new stable release of Clonezilla Live, a free Debian-based live CD designed for disk cloning tasks: "Stable Clonezilla Live 1.2.6-24 has been released. This release includes major enhancements, changes and bug fixes: the underlying GNU/Linux operating system was upgraded, it is based on the Debian 'Sid' repository as of 2010-09-21; new file system support, Btrfs, was added in this release - it has been tested successfully with Ubuntu 10.10 beta and openSUSE 11.3 restoration; Russian language was added; program makeboot.sh was improved to allow running with full path; option '--force' was added for grub-install (grub2); the Linux kernel was updated to 2.6.32-23; Partclone was updated to 0.2.15; gPXE was updated to 1.0.1...." Read the full release announcement for a complete list of changes.
* * * * *
Development, unannounced and minor bug-fix releases
|Upcoming Releases and Announcements
Summary of expected upcoming releases
New distributions added to waiting list
- Upstream OS. Upstream OS is a full-featured, openSUSE-based distribution with no-branding. Its primary feature is the ability to clone it and to build a custom distribution with the tools provided.
* * * * *
DistroWatch database summary
* * * * *
This concludes this week's issue of DistroWatch Weekly. The next instalment will be published on Monday, 4 October 2010.
Jesse Smith and Ladislav Bodnar
|Linux Foundation Training
|• Issue 840 (2019-11-11): Fedora 31, monitoring user activity, Fedora working to improve Python performance, FreeBSD gets faster networking|
|• Issue 839 (2019-11-04): MX 19, manipulating PDFs, Ubuntu plans features for 20.04, Fedora 29 nears EOL, Netrunner drops Manjaro-based edition|
|• Issue 838 (2019-10-28): Xubuntu 19.10, how init and service managers work together, DragonFly BSD provides emergency mode for HAMMER, Xfce team plans 4.16|
|• Issue 837 (2019-10-21): CentOS 8.0-1905, Trident finds a new base, Debian plans firewall changes, 15 years of Fedora, how to merge directories|
|• Issue 836 (2019-10-14): Archman 2019.09, Haiku improves ARM support, Project Trident shifting base OS, Unix turns 50|
|• Issue 835 (2019-10-07): Isotop, Mazon OS and, KduxOS, examples of using the find command, Mint's System Reports becomes proactive, Solus updates its desktops|
|• Issue 834 (2019-09-30): FreedomBox "Buster", CentOS gains a rolling release, Librem 5 phones shipping, Redcore updates its package manager|
|• Issue 833 (2019-09-23): Redcore Linux 1908, why Linux distros are free, Ubuntu making list of 32-bit software to keep, Richard M Stallman steps down from FSF leadership|
|• Issue 832 (2019-09-16): BlackWeb 1.2, checking for Wayland session and applications, Fedora to use nftables in firewalld, OpenBSD disables DoH in Firefox|
|• Issue 831 (2019-09-09): Adélie Linux 1.0 beta, using ffmpeg, awk and renice, Mint and elementary improvements, PureOS and Manjaro updates|
|• Issue 930 (2019-09-02): deepin 15.11, working with AppArmor profiles, elementary OS gets new greeter, exFAT support coming to Linux kernel|
|• Issue 829 (2019-08-26): EndeavourOS 2019.07.15, Drauger OS 7.4.1, finding the licenses of kernel modules, NetBSD gets Wayland application, GhostBSD changes base repo|
|• Issue 828 (2019-08-19): AcademiX 2.2, concerns with non-free firmware, UBports working on Unity8, Fedora unveils new EPEL channel, FreeBSD phasing out GCC|
|• Issue 827 (2019-08-12): Q4OS, finding files on the disk, Ubuntu works on ZFS, Haiku improves performance, OSDisc shutting down|
|• Issue 826 (2019-08-05): Quick looks at Resilient, PrimeOS, and BlueLight, flagship distros for desktops,Manjaro introduces new package manager|
|• Issue 825 (2019-07-29): Endless OS 3.6, UBports 16.04, gNewSense maintainer stepping down, Fedora developrs discuss optimizations, Project Trident launches stable branch|
|• Issue 824 (2019-07-22): Hexagon OS 1.0, Mageia publishes updated media, Fedora unveils Fedora CoreOS, managing disk usage with quotas|
|• Issue 823 (2019-07-15): Debian 10, finding 32-bit packages on a 64-bit system, Will Cooke discusses Ubuntu's desktop, IBM finalizes purchase of Red Hat|
|• Issue 822 (2019-07-08): Mageia 7, running development branches of distros, Mint team considers Snap, UBports to address Google account access|
|• Issue 821 (2019-07-01): OpenMandriva 4.0, Ubuntu's plan for 32-bit packages, Fedora Workstation improvements, DragonFly BSD's smaller kernel memory|
|• Issue 820 (2019-06-24): Clear Linux and Guix System 1.0.1, running Android applications using Anbox, Zorin partners with Star Labs, Red Hat explains networking bug, Ubuntu considers no longer updating 32-bit packages|
|• Issue 819 (2019-06-17): OS108 and Venom, renaming multiple files, checking live USB integrity, working with Fedora's Modularity, Ubuntu replacing Chromium package with snap|
|• Issue 818 (2019-06-10): openSUSE 15.1, improving boot times, FreeBSD's status report, DragonFly BSD reduces install media size|
|• Issue 817 (2019-06-03): Manjaro 18.0.4, Ubuntu Security Podcast, new Linux laptops from Dell and System76, Entroware Apollo|
|• Issue 816 (2019-05-27): Red Hat Enterprise Linux 8.0, creating firewall rules, Antergos shuts down, Matthew Miller answers questions about Fedora|
|• Issue 815 (2019-05-20): Sabayon 19.03, Clear Linux's developer features, Red Hat explains MDS flaws, an overview of mobile distro options|
|• Issue 814 (2019-05-13): Fedora 30, distributions publish Firefox fixes, CentOS publishes roadmap to 8.0, Debian plans to use Wayland by default|
|• Issue 813 (2019-05-06): ROSA R11, MX seeks help with systemd-shim, FreeBSD tests unified package management, interview with Gael Duval|
|• Issue 812 (2019-04-29): Ubuntu MATE 19.04, setting up a SOCKS web proxy, Scientific Linux discontinued, Red Hat takes over Java LTS support|
|• Issue 811 (2019-04-22): Alpine 3.9.2, rsync examples, Ubuntu working on ZFS support, Debian elects new Project Leader, Obarun releases S6 tools|
|• Issue 810 (2019-04-15): SolydXK 201902, Bedrock Linux 0.7.2, Fedora phasing out Python 2, NetBSD gets virtual machine monitor|
|• Issue 809 (2019-04-08): PCLinuxOS 2019.02, installing Falkon and problems with portable packages, Mint offers daily build previews, Ubuntu speeds up Snap packages|
|• Issue 808 (2019-04-01): Solus 4.0, security benefits and drawbacks to using a live distro, Gentoo gets GNOME ports working without systemd, Redox OS update|
|• Issue 807 (2019-03-25): Pardus 17.5, finding out which user changed a file, new Budgie features, a tool for browsing FreeBSD's sysctl values|
|• Issue 806 (2019-03-18): Kubuntu vs KDE neon, Nitrux's znx, notes on Debian's election, SUSE becomes an independent entity|
|• Issue 805 (2019-03-11): EasyOS 1.0, managing background services, Devuan team debates machine ID file, Ubuntu Studio works to remain an Ubuntu Community Edition|
|• Issue 804 (2019-03-04): Condres OS 19.02, securely erasing hard drives, new UBports devices coming in 2019, Devuan to host first conference|
|• Issue 803 (2019-02-25): Septor 2019, preventing windows from stealing focus, NetBSD and Nitrux experiment with virtual machines, pfSense upgrading to FreeBSD 12 base|
|• Issue 802 (2019-02-18): Slontoo 18.07.1, NetBSD tests newer compiler, Fedora packaging Deepin desktop, changes in Ubuntu Studio|
|• Issue 801 (2019-02-11): Project Trident 18.12, the meaning of status symbols in top, FreeBSD Foundation lists ongoing projects, Plasma Mobile team answers questions|
|• Issue 800 (2019-02-04): FreeNAS 11.2, using Ubuntu Studio software as an add-on, Nitrux developing znx, matching operating systems to file systems|
|• Issue 799 (2019-01-28): KaOS 2018.12, Linux Basics For Hackers, Debian 10 enters freeze, Ubuntu publishes new version for IoT devices|
|• Issue 798 (2019-01-21): Sculpt OS 18.09, picking a location for swap space, Solus team plans ahead, Fedora trying to get a better user count|
|• Issue 797 (2019-01-14): Reborn OS 2018.11.28, TinyPaw-Linux 1.3, dealing with processes which make the desktop unresponsive, Debian testing Secure Boot support|
|• Issue 796 (2019-01-07): FreeBSD 12.0, Peppermint releases ISO update, picking the best distro of 2018, roundtable interview with Debian, Fedora and elementary developers|
|• Issue 795 (2018-12-24): Running a Pinebook, interview with Bedrock founder, Alpine being ported to RISC-V, Librem 5 dev-kits shipped|
|• Issue 794 (2018-12-17): Void 20181111, avoiding software bloat, improvements to HAMMER2, getting application overview in GNOME Shell|
|• Issue 793 (2018-12-10): openSUSE Tumbleweed, finding non-free packages, Debian migrates to usrmerge, Hyperbola gets FSF approval|
|• Issue 792 (2018-1203): GhostBSD 18.10, when to use swap space, DragonFly BSD's wireless support, Fedora planning to pause development schedule|
|• Issue 791 (2018-11-26): Haiku R1 Beta1, default passwords on live media, Slax and Kodachi update their media, dual booting DragonFly BSD on EFI|
|• Issue 790 (2018-11-19): NetBSD 8.0, Bash tips and short-cuts, Fedora's networking benchmarked with FreeBSD, Ubuntu 18.04 to get ten years of support|
|• Issue 789 (2018-11-12): Fedora 29 Workstation and Silverblue, Haiku recovering from server outage, Fedora turns 15, Debian publishes updated media|
|• Issue 788 (2018-11-05): Clu Linux Live 6.0, examining RAM consumpion, finding support for older CPUs, more Steam support for running Windows games on Linux, update from Solus team|
|• Full list of all issues|
Star Labs - Laptops built for Linux.
View our range including the Star Lite, Star LabTop and more. Available with a choice of Ubuntu, Linux Mint or Zorin OS pre-installed with many more distributions supported. Visit Star Labs for information, to buy and get support.
|Random Distribution |
ADIOS Linux Boot CD
ADIOS boot CD was a Fedora-based live and installation CD with support for User Mode Linux (UML) virtual machines, further enhanced by Linux Intrusion Detection System (LIDS) and SELinux (Security Enhanced Linux). The live CD, which includes the KDE desktop environment, uses a compressed loopback filesystem.