| DistroWatch Weekly
|DistroWatch Weekly, Issue 791, 26 November 2018
Welcome to this year's 48th issue of DistroWatch Weekly!
While we usually talk about Linux distributions, with the occasional trek into BSD Land, there are a lot of open source operating systems out there. Most of them are smaller projects, often with good ideas or interesting goals, but lower visibility compared to their Linux cousins. This week we begin with a look at the noteworthy Haiku project, which strives to make a modern version of the once-popular BeOS platform. Haiku published its first beta release earlier this year and we have details on the release below, in our Feature Story. Our Opinion Poll this week also revolves around Haiku as we would like to know if the operating system fulfills your computing needs. In our Tips and Tricks section we talk about default passwords on live media, an often annoying hurdle in trying a new operating system. Plus we talk about the Slax and Linux Kodachi projects publishing minor updates to their ISO files. We are also pleased to share the new releases of the past week and list the torrents we are seeding. We wish you all a fantastic week and happy reading!
Listen to the Podcast edition of this week's DistroWatch Weekly in OGG (13MB) and MP3 (10MB) formats.
|Feature Story (by Jesse Smith)
Haiku R1 Beta1
Haiku is an open source operating system and the spiritual successor to BeOS. Haiku is a single-user operating system which offers a highly responsive desktop interface and strives to be easy to use. Development of Haiku started in 2001 and the initial release came out in 2002. Development of Haiku has been gradual and the project released its first beta in September of 2018.
According to the project's release notes, Haiku requires just 256MB of memory and 3GB of disk space. The operating system includes a number of useful utilities, a virtual terminal, a system installer and a web browser (called WebPositive). Haiku's first beta also includes a new network connection tool and a different approach to package management.
By far the largest change in this release is the addition of a complete package management system. Finalized and merged during 2013 thanks to a series of contracts funded from donations, Haiku's package management system is unique in a variety of ways. Rather than keeping a database of installed files with a set of tools to manage them, Haiku packages are a special type of compressed filesystem image, which is 'mounted' upon installation (and thereafter on each boot) by the packagefs, a kernel component. This means that the /system/ hierarchy is now read-only, since it is merely an amalgamation of the presently installed packages at the system level (and the same is true for the ~/config/ hierarchy, which contains all the packages installed at the user level), ensuring that the system files themselves are incorruptible.
The download for Haiku is a compressed archive 887MB in size. Unpacking the archive gives us an ISO file that is about 1.1GB. Booting from the provided media brings up a window asking us to select our preferred language from a list. We can then launch the Haiku system installer or try the live desktop environment.
The live desktop features seven icons lined up along the top of the screen. Over in the upper-right corner of the desktop is an application menu (represented by a blue feather), a system tray and a list of open windows. The desktop seems designed to use space as efficiently as possible; the visible elements are mostly small and tucked away into the corners.
Haiku R1 Beta1 -- The application menu
(full image size: 132kB, resolution: 1280x1024)
Looking over the desktop icons we find some that open the file manager, one which opens BeBook (which appears to be a developer guide), one that opens a welcome document and one that opens the user guide. The welcome document and user guide both provide some useful tips on using the desktop, installing wireless network support and the file system layout. The documentation is clear, features examples and often includes screen shots.
Haiku's system installer can be launched from the live desktop's greeter or from an icon on the desktop. The installer is very short and simple. We are asked to select the location of source packages (with the default location being the DVD). The only other thing the installer wants to know is where Haiku should be installed with available partitions being shown in a drop-down box. If no suitable partition is available we can click a button to launch DiveSetup, a graphical partition manager similar to GParted. Once we have selected an empty partition, the installer copies its files to the hard drive. The entire install process takes about 30 seconds. When it is finished, we can continue to use the live environment or restart the computer to use our new copy of Haiku.
The locally installed copy of Haiku boots directly to the desktop. The installed desktop is virtually identical to the live desktop, except the system installer icon has been removed. The graphical interface is amazingly responsive with new programs and windows opening almost instantly.
Something that took me a while to get used to is Haiku's windows are not entirely rectangular as on most other modern operating systems. Haiku's windows have a little tab that sticks out of the top that acts as the title bar and includes buttons to close and maximize windows. I also found maximizing a window does grow the window while avoiding covering the application menu. This feature, along with the upper window tab, means maximized windows leave empty screen space above and to the right (ie. they don't look maximized).
Haiku's application menu features options for accessing files, shutting down the computer, or browsing installed programs. There are also menu trees for accessing settings and demo programs. Each menu tree is arranged in alphabetical order without any sub-menus for categories of programs. I suspect that, over time, this will make the menus quite full and increasingly slower to navigate. However, in its default state, I found the menu tress easy to explore and most applications are clearly labelled; program names tend to match their functionality. For example, the archive manager is called Expander, the partition manager is called DriveSetup, and the addressbook is simply called People.
I experimented with Haiku in a VirtualBox virtual machine and on my physical workstation. When I tried running Haiku on the physical machine the operating system failed to complete the boot process. The graphical splash screen would display for a few seconds, but the system would lock up prior to getting the to desktop. This happened when booting in both UEFI and legacy BIOS modes.
When running in VirtualBox, Haiku did not integrate with the host environment. I was, however, able to make use of my system's full screen resolution by adjusting the display dimensions in Haiku's Screen configuration tool. The virtual machine used a lot of my host's CPU. Even when Haiku was idle, VirtualBox was using 25% of my host's CPU resources. Running a simple application such as the resource monitor in Haiku raised that usage to 35%.
Haiku has a pleasantly small footprint, using about 350MB of RAM when sitting idle at the desktop. The operating system, once installed, used 2.7GB of disk space, which is relatively light compared to most modern Linux distributions.
Haiku comes with several applications already installed. The WebKit-based WebPositive browser is featured, along with a Mail client. There is also a simple media player, the Pe text editor, a partition manager and a disk usage monitor. There is an audio recorder, a contact manager and a very simple web server called PoorMan which allows us to share a directory over the HTTP protocol. There is an application called TV which just shows a test pattern image and, so far as I could tell, won't do anything else as the menu for channels contains no additional entries. There is an IRC client called Vision, which is a rare exception to Haiku's obvious naming scheme for applications.
Haiku R1 Beta1 -- Reading documentation in WebPositive
(full image size: 128kB, resolution: 1280x1024)
If we open a virtual terminal, Haiku presents us with the Bash shell. From the shell we can use most Unix command line tools, view manual pages and connect to remote computers using OpenSSH. The GNU Compiler Collection is installed for us in case we want to build new applications.
The media player was able to handle playing audio and video files. Playback was pleasantly smooth, even in the virtual machine environment. The one issue with media playing I ran into was stopping a video and trying to restart it from the beginning would cause the player to stop working. I had to close the player and re-open it to restart a video.
Another quirk I ran into was clicking the Help menu entry in the Pe editor would open WebPositive and display Haiku's website. A more pleasant feature I enjoyed was the terminal would change the colour of the shell prompt depending on whether the previous command had completed successfully. This gave a clear indication as to whether programs were completing their work properly.
A consistent problem I kept running into was Haiku's network connection dropped every few minutes. I could get on-line, visit a web page or two, but then the connection would drop. This would cause WebPositive, or whichever application I was using, to lock-up and refuse to either continue or close. Haiku's applications do not handle losing their network connection gracefully and need to be terminated from the command line.
I tried various different network settings in the hope that using a static IP, or different DNS, or a bridged connection would solve my connection issues. However, in the end, I typically just succeeded in locking up the network manager rather than re-establishing a connection to the Internet. The only reliable solution was to reboot Haiku to bring the network connection back on-line.
Programs are added to Haiku through a desktop utility called HaikuDepot. The depot is divided into two panes. The top pane displays a list of available applications in alphabetical order. Each entry includes the program's name, an icon and a brief description. Some feature a rating out of five stars. Clicking on an application causes the bottom pane to display a detailed description and a screen shot. Once a program has been highlighted we can install it with a single click.
Haiku R1 Beta1 -- The software manager
(full image size: 125kB, resolution: 1280x1024)
The depot is easy to navigate though it shows a lot of software and there is no separation of applications into different categories, as many modern software managers do. If we are looking for a specific program or an application to handle a specific task we can perform searches using key words. Searching for "office" for example, will bring up the entry for LibreOffice.
While HaikuDepot is easy to navigate, I was never able to successfully complete an installation as my network connection kept dropping. I ran into a similar problem when using the update manager, SoftwareUpdater. The update manager, which must be run manually, displays a list of available updates with a short description next to each. We can then click a button to download the waiting items. When I started using Haiku there were 31 new updates waiting. My network connection never remained stable long enough to download more than 22 of the waiting packages.
Haiku R1 Beta1 -- Software updates
(full image size: 82kB, resolution: 1280x1024)
As you can probably tell by this point, I ran into a number of frustrating problems while using Haiku. The main ones were the network connection constantly dropping every few minutes, and the operating system failing to boot on my workstation. There were some other aspects that I wasn't thrilled about - the title bar being a tab at the top of windows looks weird and inefficient to me, but that is a matter of taste.
Having an operating system which only has one user account and doesn't require passwords is a non-starter for me. Some people may like the convenience and simplicity of having a completely open, one-user system (it does streamline things) but it wouldn't be suitable for any of my environments or devices, apart from my mobile phone.
In short, in my situation and in my environments, Haiku is not a practical option. However, there are several aspects of the operating system and its surrounding project that I think are great. Haiku has unusually clear and well organized documentation. Most open source projects could use Haiku as an example of how to make user guides. There are little details I like, for example the notes on how to set up wireless networks are available locally, on the install media. This is a minor detail, but it's unfortunate how many projects explain how to get on-line in resources which are only available on-line.
Haiku's desktop is clean, the look is consistent across applications and visual elements don't use up much space. It took me some time to get used to having the application menu and task switcher on the right side of the screen instead of the left, but I like the way the desktop is presented.
One of Haiku's best features is that it is fast and responsive. Whether the system is booting, launching programs, browsing the web or displaying a video, the desktop is highly responsive. Everything feels light and reacts almost instantly to input. This is behaviour I usually only see in super light (and minimal) Linux window managers and I really appreciated the how everything happens quickly on Haiku.
So while Haiku is not practical for me, and I'm guessing for many people, I do think there are aspects of the project which should be held up as a good way to do things in the open source community. I must also applaud Haiku's team for porting several applications, including LibreOffice, to their operating system. Haiku has a lot of its own applications, but I think many users will appreciate having ports of popular programs in the HaikuDepot.
* * * * *
Hardware used in this review
My physical test equipment for this review was a desktop HP Pavilon p6 Series with the following specifications:
- Processor: Dual-core 2.8GHz AMD A4-3420 APU
- Storage: 500GB Hitachi hard drive
- Memory: 6GB of RAM
- Networking: Realtek RTL8111 wired network card
- Display: AMD Radeon HD 6410D video card
* * * * *
Visitor supplied rating
Haiku has a visitor supplied average rating of: 7.8/10 from 24 review(s).
Have you used Haiku? You can leave your own review of the project on our ratings page.
|Miscellaneous News (by Jesse Smith)
Slax and Kodachi update their download media, dual booting DragonFly BSD
The Slax distribution, a live operating system based on Debian, was recently updated to version 9.6.0. The new version was then quickly replaced by a series of minor updates over the course of the week, concluding with Slax 9.6.3. The project's leader, Tomáš Matějíček, explained the reason for the series of minor updates: "While I was repackaging ISO for the 64-bit version of Slax 9.6.1, I used Midnight Commander to extract the ISO contents. Unfortunately I forgot that there is a bug in Midnight Commander and it does not see empty directories. For that reason, the Slax 9.6.2 ISO file did not contain a /slax/changes directory, which is needed for storing persistent changes. You can fix that yourself easily by simply creating that directory. I've already pushed out version 9.6.3, which fixes this."
* * * * *
The Linux Kodachi project discovered a problem with the software shipped on the distribution's 5.3 release and published new media to address the problem. Unlike the Slax project which bumped its version number for the new media, Kodachi has kept the same version number and published a new checksum on Twitter: "If you have downloaded Kodachi 5.3 before 22-Nov-2018 please re-download again because I have fixed a bug to do with Nordvpn and force traffic via VPN." The tweet includes the new checksum.
* * * * *
Getting multiple operating systems to play well beside each other on the same disk, a practise known as dual booting, can be tricky. For people who want to run DragonFly BSD on the same hardware as other operating systems on an EFI-enabled computer, the DragonFly BSD Digest blog has some suggestions. "If you were looking to run DragonFly on the same disk as another operating system, Dr. Martin Ivanov has advice for you. Similarly, karu.pruun and Pierre-Alian TORET also have something on EFI booting."
* * * * *
These and other news stories can be found on our Headlines page.
|Tips and Tricks (by Jesse Smith)
Default passwords on live media
One of the questions I see most frequently in my inbox comes from people who have downloaded new installation or live media and found themselves presented with a password prompt. Then, because the default credentials are not included on the distribution's download page or in the release notes, they e-mail me and ask: "What is the default password for <insert project name here>?" It happens fairly frequently and I think it goes to show that many open source developers are not doing a great job of anticipating their users' experiences and communicating key information. I think there are actually four small problems in evidence here:
As it happens, I usually do not know, off the top of my head, what every distribution's default password is. My memory is pretty good most days, but I have my limits. However, most default usernames and passwords for distributions' live media will be one of the following:
- There is a password prompt. This usually should not happen on live media. The user should typically be signed in automatically and the screen, ideally, should not lock on a live session, unless the user requests it. If the user is being asked for a password prompt when running from a live disc, it could probably be considered a bug.
- I suspect that a prompt for an unknown password indicates that no one outside the development team is testing the operating system. If you sit a non-techie friend or family member in front of a live disc that boots to a login screen, the first thing they are likely to do is ask what the password is. This is a good sign the prompt should be skipped or the password should be published somewhere obvious. Whenever I see a password prompt on a live disc, the thought crosses my mind: "This operating system has not been subjected to outside testing."
- Related to the second point, if a password prompt is really necessary, then the default, live password should be published somewhere obvious. The release announcement and/or the download page should tell potential users how to login. Otherwise their trial is only going to last 30 seconds and then they will give up.
- Developers often make it difficult to contact them or hard to find the password on their website. People would not be looking up my e-mail address and asking me about sign in credentials for random operating systems if the information were easy to find on the project's website. This only serves to make the operating system seem less user friendly and suggests there is a lack of useful documentation.
Whenever you find yourself staring at a password prompt, unsure of what to type, I suggest trying one of the above passwords, then filing an issue with the distribution. If you are stuck that means other people are too and the developers should be made aware there is a problem so they can update their documentation or automate the login procedure.
- <blank> (just press Enter to sign in)
- toor (root spelled backwards)
- <the name of the distribution> (SuperOS will probably use "superos" as their username and password)
* * * * *
More tips can be found in our Tips and Tricks archive.
|Released Last Week
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: 1,134
- Total data uploaded: 22.3TB
|Upcoming Releases and Announcements
Summary of expected upcoming releases
Does Haiku suit your needs?
In our review this week of Haiku we discussed some of the operating system's perks (such as its light, responsive desktop) and drawbacks (limited hardware support and single-user access). We would like to know what our readers think of Haiku. Does it suit your computing needs? Have you set it up on a relative's computer who just needs to browse the web and check e-mail? Let us know your impressions of Haiku in the comments.
You can see the results of our previous poll on size and frequency of package updates in last week's edition. All previous poll results can be found in our poll archives.
Does Haiku suit your needs?
|Haiku does cover all my computing needs: ||95 (8%)|
| Haiku does not cover my needs but works for my friends/family: ||84 (7%)|
| Haiku does not cover my needs or those of my friends/family: ||535 (46%)|
| Not sure yet: ||437 (38%)|
DistroWatch database summary
* * * * *
This concludes this week's issue of DistroWatch Weekly. The next instalment will be published on Monday, 3 December 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)
|Linux Foundation Training
|• Issue 848 (2020-01-13): elementary OS 5.1, accessing USB ports directly, NetBSD expanding Wayland support, Fedora phasing out old Python packages|
|• Issue 847 (2020-01-06): Android-x86 9.0, Hypberbola switching to BSD base, Debian votes on init diversity, slow adoption of Wayland and delta packages|
|• Issue 846 (2019-12-23): NomadBSD 1.3, Tails publishes boot fix, Arch update requires intervention, Purism launches server lineup, password protecting files|
|• Issue 845 (2019-12-16): OpenIndiana 2019.10, BunsenLabs' "Lithium" preview, MX-Fluxbox, 10 years of Tails, installing local packages|
|• Issue 844 (2019-12-09): Project Trident Void alpha, alpha installer for "Bullseye", SparkyLinux portable edition, dealing with large log files|
|• Issue 843 (2019-12-02): Obarun 2019.11.02, Bluestar 5.3.6, using special characters on command line, Fedora plans to disable empty passwords, FreeBSD's quarterly status report|
|• Issue 842 (2019-11-25): SolydXK 10, System Adminstration Ethics book review, Debian continues init diversity debate, Google upstreaming Android kernel patches|
|• Issue 841 (2019-11-18): Emmabuntus DE3-1.00, changing keys in keyboard layout, Debian phasing out Python 2 and voting on init diversity, Slackware gets unofficial updated live media|
|• 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 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 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 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 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, 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 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|
|• 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 |
redWall Firewall was a bootable CD-ROM firewall based on Gentoo Linux. Its goal was to provide a feature-rich firewall solution together with a web-based interface for all the generated log files. redWall Firewall comes with Snort, SnortSam, DansGuardian and support for fwbuilder, SpamAssassin, reporting, VPN and mail alerts. Configuration files are stored on a floppy disk or a USB pen drive.