Language Selection

English French German Italian Portuguese Spanish

Mini Distro Round-Up

Filed under
Reviews

I went to distrowatch and looked for the 5 smallest distros I could find. I found my old pal Damn Small Linux, new comers Puppy Linux, Feather Linux, BeatrIX, and Sam.

I sampled each of those listed above and will share my thoughts and screenshots of them with you. I also thought to make it more fair, I'd outline and define some criteria for them to meet. Not scientific, but I chose five areas that I considered important in which a mini distro should excel. Each distro has the opportunity to earn 5 points for each of the 5 areas. Then I will divide that total by 5 to get their final score of between 1 and 5 points.

  • Size:
  • The smallest in the lot was 50mb, so that was my starting point. In my tests and for the purposes of this article, smaller is better.

  • Ease of Use:
  • Is it easy to boot up and get into a gui? Are the tools and applications readily available and easy to find, and easy to use?

  • Looks:
  • Simply put, how pleasing is it to the eye?

  • Useful:
  • Are the apps included useful and are they useful to a majority of users? Is there something included to complete most any basic task? This area is most simply put, how useful is the distro?

  • Stability and Functionality:
  • Is the distro stable and are the applications stable? Do they function as designed and complete their tasks?


The Contenders

Damn Small Linux is the coolest thing in my book if for no other reason than it's itty bitty size. To get a fully functional operating system complete with X server in 50 mb is quite the accomplishment. I found it and puppy linux to have met that criteria. damn small linux claims to be able to run light enough to power a 486DX with 16MB of Ram.

dsl is a complete operating system containing a mighty powerful toolbox. in it's gui you'll find office tools such as a spreadsheet, several editors and a couple word processors, as well as graphic manipulation/editing tools. It comes with games, multimedia applications, and system monitoring tools. Included are the means for a harddrive install and even application installation and updating. There are tools for your networking options and connecting to remote desktops, virtual file systems, and even ftp servers. Found are file managers, web browsers, mail and instant messaging clients. Of course it goes without saying, it also comes with a full compliment of commandline tools. Most applications were carefully chosen for their balance of functionality, stability, and size.

Being built upon Knoppix, dsl's hardware detection was good and fairly accurate. Most of my hardware was detected and the correct module was inserted accordingly. My network connection worked automagically, it having used dhcp. The X server booted into a nice looking Fluxbox desktop with 1024x768 resolution.

I found dsl to be fast, stable, fully functional and a wondrous thing. It was my favorite of all the mini-distros I sampled. I've always been a fan and even until a recent harddrive death, had a permanent install of it taking up about 250 mbs. And it's got the coolest name! Big Grin

Screenshots

Puppy Linux was just a big bag of surprizes from the moment it began to boot until I logged out. This was my first test drive of puppy linux, so perhaps that contributed to my impression. The first notable was the amazing lack of time it took to boot. It had to have been no more than 30 seconds before I was looking at a question about which mouse dev I wanted to use. I choose imps/2 and wondered if it would work, yes it did. It asked did I have a scroll wheel, and within 2 seconds of clicking yes I was presented with a gui.

Upon entering the auto-logged in gui, I was asked which resolution I wanted to use. Choosing 1024x768x16 seemed like a good choice, it adjusted and staring at me was a nice fvwm desktop. The menu reminded me of a cross between kde's and windows', but the start button did come with a cute little puppy icon. Inside that menu was a plethora of software. It's hard to believe this was from a 56mb iso.

My internet connection wasn't enabled automagically, but a simple "dhcpcd" command was all that was needed to surf the internet and even my lan's samba shares.

Import and xwd weren't installed, but xpaint can take screenshots, even if a bit cumbersome. Looking around lo-and-behold there was a menu entry for xpaint gui screenshots. Well, I didn't like all that clicking to get a screenshot and man xpaint opened a browser with the commands I could use.

The menu was chocked full of applications. There were gui apps for about everything from configuring the desktop, monitoring the system, connecting to about everything under the sun, to all sorts of movie and music players. I was throughly impressed. Not only did it have a couple browsers, but it had at least two html editors. It even had a puppy-get software installer. Some of the utilities present were backup to cd, F-Prot virus scanner, and guiTar archiver. Also included was a menu item for a gui mount tool, which was nice because I couldn't get the mount command to work. It kept saying such and such directory didn't exist. I suppose it had to do with it's method of ramfs. But it did find and let me mount a partition/directory in which I could save my screenshots.

Puppy Linux seemed to derive from Debian and came with a 2.4.27 kernel. It was a wonderful wonderful little distro. I was thoroughly impressed, I might have to put that one on it's own partition somewhere. Smile Kudos to the developers.

Screenshots

Feather Linux is the prettiest mini distro so far, also based on Knoppix and comes with a 2.4.27 kernel. A little larger than dsl or puppy weighing in at a 120mb. Like puppy, it boots really fast and asks some configuration questions along the way. Default lang and keyboard are german, I had to specify lang=us at boot. As puppy did it asked what kinda mouse I had and in what resolution I wanted X to run, and in addition it asked about default keymap.

The desktop was just pretty as all get out with cute tux wallpaper and nice icons. Default desktop is fluxbox and it's using a nice matching theme.

It's menus were full of apps, maybe not as much as puppy seemed, but still quite a toolkit. It comes with all the standard applications for web browsing, im, irc, email, ftp, ssh, samba, word processing, image manipulation, various multimedia capabilities, and standard commandline apps and built-ins. It was fast, stable and complete.

The author describes it as "a Linux distribution which runs completely off a CD or a USB pendrive and takes up under 115Mb of space. It is a Knoppix remaster (based on Debian), and tries to include software which most people would use every day on their desktop."

Screenshots

BeatrIX Linux is a whoping 183mb, yet it seemed to have the less to offer. This developer chose to go with a few big heavy apps as opposed to our other candidates who went with a more complete outfit of smaller applications. BeatrIX does come with a browser, an instant messenger, an email and an office app. But they are about the biggest heaviest example of each. Mozilla-Firefox, Gaim, Evolution, and OpenOffice are kinda big and slow applications. I didn't see a graphical file manager. I suppose with 6 full page consoles of binaries tho, it's bound to have had one - just no desktop icon or menu entry for it. To top it off, it's all sitting on Gnome 2.8 and running on a 2.6.7 kernel. It does have a cute start up slogan though: BeatrIX - Linux that purrs.

BeatrIX is named after a cat and the developers stress that it isn't designed for multimedia. They state, "it simply works and is easy to learn and use. Months were spent on designing the desktop to be as usable as possible the first time you insert the BeatrIX CD."

It was slower than it's competition so far, and it's by far not the prettiest. But it does indeed do as it's designed. It's still relatively small, but it won't fit on my mini-cds. All and all, BeatrIX just isn't my cup of tea. I imagine gnome fans might like it though.

Screenshots

Sam Linux "is a bootable Linux-CD based on Mandrakelinux, an installation on harddrive is not necessarily, but possible. Because of the small size of under 210mb it fits on a 8cm-mini-CD and is ideal for carrying in the pocket. Although it is so small, it contains a full graphical desktop environment with office-, internet-, multimedia- and graphics-applications, even some games and a small server-section are there." ...so they say.

It is also the only distro in this round-up that won't run on my desktop computer. It booted, but then locked up as it tried to enter X. In fact it locked up so hard that I had to hit reset...

So, anyway, it will run on my older computer with an ati rage 128 and I was able to gleen some information from there. I wasn't able to get screenshots as it locked up solid as I was trying to su to root. The password is supposed to be "root" according to the site, but it was rejected and on the third try it locked the computer up tight as a drum. I'm not trying anymore.

Sam appears to be using Xfce for it's window manager with gnome commander, velocity, midnight commander, and Xffm listed as file managers. It comes with Dillo and Firefox for web browsing, Sylpheed for email and Pan for newsreading. Included is gaim for instant messaging, Xchat for irc and Skype for voip. Sam is the first one of our minis to use TextMaker for it's word processing, to include a personal finance tool and something to use your bttv card for watching tv. It even comes with gimp and more than just a few games. Also included are the Mandrake Control Center, firestarter and a harddrive installer.

So, all in all, this distro is as buggy as it's roots. I can't recommend Sam Linux as I didn't even get to test drive it much past menu navigation before it locked up.

Luit Linux is another 50mb mini distro based on damn small linux. It's getting long in the tooth as the lastest release I saw was July 2004. It's using a 2.4.22-xfs kernel dated September 2003 underneath an older XFCE. However it did fine on my system, hardware newer than that kernel date.

It booted quickly and performed well. It had some applications for doing basic tasks and all seemed stable except for it's choice in a spreadsheet app. It didn't open when clicked upon. Otherwise it's another adequate mini, although I wasn't highly impressed. I suppose it's stagnating development was a turn-off from the start.

Screenshots

The Verdict


Distro Size Ease Looks Useful Stab/Funct total/5
Damn Small 5 4 3 4 5 4.2
Puppy 5 3 3 4 5 4
Feather 4 4 5 4 5 4.4
BeatrIX 3 4 2 3 4 3.2
Sam 2 3 3 2 0 2
Luit 5 3 3 3 4 3.8


In conclusion, I still like damn small linux the best although puppy linux is a very close second. Seems the points favor feather linux, and it was indeed the prettiest. Any of these three can fill the bill for about any rescue or convenient take along purpose you might have. Beatrix is too big and heavy for no more than it offers and Sam, well, my mama said if you can't say anything nice...

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

re: I concur!

I don't know why Sam didn't want to run here. At first I thought it must be my newer video card, a geforce 6800oc, but then it locked up with an old ati rage 128 too. I'm using AMD 2800+ barton on a MSI KT4AV (kt400) with crucial pc2700 ddr in one and a 2200+ thunderbird on a Abit KX7-333 (kt333) with kingston pc2700 in the other.

I wish I had seen this link yesterday tho, I'da skipped the Sam report altogether. Tongue

----
You talk the talk, but do you waddle the waddle?

re: Be l337 with Luit!

yep, that's the one I was talking about wishing I had seen the link yesterday. I saw it today on pclo after writing my article. I've already downloaded it and burnt it, but I'm having issues with my slave server, so I may not get around to updating my article with it's coverage.

In addition, am I just not seeing a newer release than last July?

thanks.

----
You talk the talk, but do you waddle the waddle?

Updated to include Luit.

Thanks for the encouragement, I updated the article to include Luitlinux.

----
You talk the talk, but do you waddle the waddle?

re: It seems that Flonix is not r

I saw it listed on distrowatch and looked at the site, but it looked like usb was the only method. This seems to be the download link. I guess I could have made it work on cdr. Perhaps I dismissed it too quickly. Well, it's back to the salt mines today. I'll have to save that one for another day.

----
You talk the talk, but do you waddle the waddle?

re: They all seem to borrow from DSL

Yep, I noticed that too.

Thanks! Smile

----
You talk the talk, but do you waddle the waddle?

oh ok, I see

Yeah, that link posted yesterday in a previous reply /was/ for a bootable cdrom. I was running too late yesterday and looked at it too quickly. I guess the bootable usb key could be nice for some tho. But I don't know when it might be /more/ convenient than a mini cd. Anyone know any examples?

----
You talk the talk, but do you waddle the waddle?

re: new puppy

wow, you should have submitted that as news. Smile

sounds wonderful.

----
You talk the talk, but do you waddle the waddle?

re: Wot about the Latvians?

I spent a coupla days clicking on about every link at distrowatch to look at the size of the iso trying to find the 5 or 6 smallest. Perhaps we can do a part 2 or something.

Thanks for your comments! Smile

----
You talk the talk, but do you waddle the waddle?

re: future of tiny Linux?

I hear ya! I think that's why I have such a soft spot for mini distros. It takes development to a whole new level by trying to keep the download at 50 mb while still remaining (relatively) full featured.

And yes there are several that I didn't get to look at then. So many Linuxes, so little time. Big Grin

----
You talk the talk, but do you waddle the waddle?

TinyMe?

You should have tried TinyMe instead of SAM, IMO. It's more in the same vein as Puppy and DSL. It's a shame you didn't get SAM working. It's a very good distro.

re: tinyme

This is an older article. TinyMe wasn't around then. Sam became much more usable subsequently and TinyMe is very nice as well.

More in Tux Machines

Programming: WebAssembly, Mozilla GFX, Qt and Python

  • WebAssembly for speed and code reuse

    Imagine translating a non-web application, written in a high-level language, into a binary module ready for the web. This translation could be done without any change whatsoever to the non-web application's source code. A browser can download the newly translated module efficiently and execute the module in the sandbox. The executing web module can interact seamlessly with other web technologies—with JavaScript (JS) in particular. Welcome to WebAssembly. As befits a language with assembly in the name, WebAssembly is low-level. But this low-level character encourages optimization: the just-in-time (JIT) compiler of the browser's virtual machine can translate portable WebAssembly code into fast, platform-specific machine code. A WebAssembly module thereby becomes an executable suited for compute-bound tasks such as number crunching. Which high-level languages compile into WebAssembly? The list is growing, but the original candidates were C, C++, and Rust. Let's call these three the systems languages, as they are meant for systems programming and high-performance applications programming. The systems languages share two features that suit them for compilation into WebAssembly. The next section gets into the details, which sets up full code examples (in C and TypeScript) together with samples from WebAssembly's own text format language.

  • Mozilla GFX: moz://gfx newsletter #47

    Hi there! Time for another mozilla graphics newsletter. In the comments section of the previous newsletter, Michael asked about the relation between WebRender and WebGL, I’ll try give a short answer here. Both WebRender and WebGL need access to the GPU to do their work. At the moment both of them use the OpenGL API, either directly or through ANGLE which emulates OpenGL on top of D3D11. They, however, each work with their own OpenGL context. Frames produced with WebGL are sent to WebRender as texture handles. WebRender, at the API level, has a single entry point for images, video frames, canvases, in short for every grid of pixels in some flavor of RGB format, be them CPU-side buffers or already in GPU memory as is normally the case for WebGL. In order to share textures between separate OpenGL contexts we rely on platform-specific APIs such as EGLImage and DXGI. Beyond that there isn’t any fancy interaction between WebGL and WebRender. The latter sees the former as a image producer just like 2D canvases, video decoders and plain static images.

  • The Titler Revamp: QML Producer in the making

    At the beginning of this month, I started testing out the new producer as I had a good, rough structure for the producer code, and was only facing a few minor problems. Initially, I was unclear about how exactly the producer is going to be used by the titler so I took a small step back and spent some time figuring out how kdenlivetitle worked, which is the producer in use. Initially, I faced integration problems (which are the ones you’d normally expect) when I tried to make use of the QmlRenderer library for rendering and loading QML templates – and most of them were resolved by a simple refactoring of the QmlRenderer library source code. To give an example, the producer traditionally stores the QML template in global variables which is taken as a character pointer argument (which is, again, traditional C) The QmlRenderer lib takes a QUrl as its parameters for loading the Qml file, so to solve this problem all I had to do was to overload the loadQml() method with one which could accommodate the producer’s needs – which worked perfectly fine. As a consequence, I also had to compartmentalise (further) the rendering process so now we have 3 methods which go sequentially when we want to render something using the library ( initialiseRenderParams( ) -> prepareRenderer( ) -> renderQml( ) ) [...] The problem was resolved (thank you JB) finally and it was not due to OpenGL but it was simply because I hadn’t created an QApplication for the producer (which is necessary for qt producers). The whole month’s been a steep curve, definitely not easy, but, I enjoyed it! Right now, I have a producer which is, now, almost complete and with a little more tweaking, will be put to use, hopefully. I’m still facing a few minor issues which I hope to resolve soon and get a working producer. Once we get that, I can start work on the Kdenlive side. Let’s hope for the best!

  • How to Make a Discord Bot in Python

    In a world where video games are so important to so many people, communication and community around games are vital. Discord offers both of those and more in one well-designed package. In this tutorial, you’ll learn how to make a Discord bot in Python so that you can make the most of this fantastic platform.

  • Qt Visual Studio Tools 2.4 RC Released

    The Visual Studio Project System is widely used as the build system of choice for C++ projects in VS. Under the hood, MSBuild provides the project file format and build framework. The Qt VS Tools make use of the extensibility of MSBuild to provide design-time and build-time integration of Qt in VS projects — toward the end of the post we have a closer look at how that integration works and what changed in the new release. Up to this point, the Qt VS Tools extension managed its own project settings in an isolated manner. This approach prevented the integration of Qt in Visual Studio to fully benefit from the features of VS projects and MSBuild. Significantly, it was not possible to have Qt settings vary according to the build configuration (e.g. having a different list of selected Qt modules for different configurations), including Qt itself: only one version/build of Qt could be selected and would apply to all configurations, a significant drawback in the case of multi-platform projects. Another important limitation that users of the Qt VS Tools have reported is the lack of support for importing Qt-related settings from shared property sheet files. This feature allows settings in VS projects to be shared within a team or organization, thus providing a single source for that information. Up to now, this was not possible to do with settings managed by the Qt VS Tools.

Screenshots/Screencasts: 10 GNU/Linux Distros (Screenshots) and New Screencast/Video of Endeavour OS 2019.08.17

  • 10 Linux distros: From different to dangerous

    One of the great benefits of Linux is the ability to roll your own. Throughout the years, individuals, organizations, and even nation states have done just that. In this gallery, we're going to showcase some of those distros. Be careful, though. You may not want to load these, or if you do, put them in isolated VMs. We're not kidding when we say they could be dangerous.

  • Endeavour OS 2019.08.17 Run Through

    In this video, we are looking at Endeavour OS 2019.08.17.

A Cycle of Renewal, Broken: How Big Tech and Big Media Abuse Copyright Law to Slay Competition

In 1950, a television salesman named Robert Tarlton put together a consortium of TV merchants in the town of Lansford, Pennsylvania to erect an antenna tall enough to pull down signals from Philadelphia, about 90 miles to the southeast. The antenna connected to a web of cables that the consortium strung up and down the streets of Lansford, bringing big-city TV to their customers — and making TV ownership for Lansfordites far more attractive. Though hobbyists had been jury-rigging their own "community antenna television" networks since 1948, no one had ever tried to go into business with such an operation. The first commercial cable TV company was born. The rise of cable over the following years kicked off decades of political controversy over whether the cable operators should be allowed to stay in business, seeing as they were retransmitting broadcast signals without payment or permission and collecting money for the service. Broadcasters took a dim view of people using their signals without permission, which is a little rich, given that the broadcasting industry itself owed its existence to the ability to play sound recordings over the air without permission or payment. The FCC brokered a series of compromises in the years that followed, coming up with complex rules governing which signals a cable operator could retransmit, which ones they must retransmit, and how much all this would cost. The end result was a second way to get TV, one that made peace with—and grew alongside—broadcasters, eventually coming to dominate how we get cable TV in our homes. By 1976, cable and broadcasters joined forces to fight a new technology: home video recorders, starting with Sony's Betamax recorders. In the eyes of the cable operators, broadcasters, and movie studios, these were as illegitimate as the playing of records over the air had been, or as retransmitting those broadcasts over cable had been. Lawsuits over the VCR continued for the next eight years. In 1984, the Supreme Court finally weighed in, legalizing the VCR, and finding that new technologies were not illegal under copyright law if they were "capable of substantial noninfringing uses." Read more

Software, HowTos and Storage

  • Pause Music When Locking The Screen And Resume On Unlock For Spotify, Rhythmbox, Others

    When you lock your computer screen (without suspending the system), most desktop audio players continue playback in the background, sometimes not emitting any sound ¹. Due to this you may unintentionally skip parts of podcasts or songs in a playlist, etc. Enter pause-on-lock, a Bash script that pauses your music player when you lock the screen and resumes playback once the screen is unlocked. pause-on-lock works on Unity, GNOME, Cinnamon and MATE desktop environments, and by default it supports Spotify and Rhythmbox. With the help of playerctl (a command line controller for controlling media players that support the MPRIS D-Bus interface), this script can extend its supported music players to many others, including Audacious, VLC, Cmus, and others.

  • Easy Way to Screen Mirroring Android on Ubuntu!

    Screen Mirroring is one of the features found on smartphones, one of which is on Android. This feature serves to display the smartphone to a computer. This is very useful for example when used for demo applications that you make, or maybe for other things related to smartphones. In Ubuntu, we can do screen mirroring with applications available on Android, for example is AirDroid which can be used for screen mirroring through a browser. But I feel less optimal when using this instant method. Because there is a lag between activity on the smartphone and on the monitor screen on the computer, and the results are less than optimal. What might be the cause because it is opened through a browser and uses wi-fi? (Personal question). I am looking for another application for screen mirroring on Ubuntu, and one of the very good applications is Scrcpy. This application can be used for screen mirroring without a root device.

  • Command line quick tips: Searching with grep
  • How to Install Cezerin on Debian 9
  • How to Create a Bootable USB Stick from the Ubuntu Terminal
  • How to Install Git on Debian 10
  • How to Copy/Move a Docker Container to Another Host
  • Six practical use cases for Nmap
  • The Next Stage of Flash Storage: Computational Storage
  • NAS upgrade

    At some point in the future I hope to spend a little bit of time on the software side of things, as some of the features of my set up are no longer working as they should: I can't remote-decrypt the main disk via SSH on boot, and the first run of any backup fails due to some kind of race condition in the systemd unit dependencies. (The first attempt does not correctly mount the backup partition; the second attempt always succeeds).

  • Storage Concepts And Technologies Explained In Detail