SliTaz armhf: 46MB Linux Distribution for Raspberry Pi

SliTaz armhf is a minimal Linux distribution based on SliTaz Linux, that uses the hard-float ABI for the Raspberry Pi. The compressed SD card image is 46M, the rootfs 18.6 MB, and Slitaz uses just about 7 MB RAM after boot.

Slitaz armhf rootfs comes pre-loaded with the following packages:

  • busybox 1.20.2
  • dropbear 2012.55 – Light SSH client and server.
  • nano 2.2.6 – GNU Nano Text Editor.
  • retawq 0.2.6c –  Text mode Web browser.
  • tazpkg 5.0 – SliTaz packages manager (Tiny autonomous zone packages manager).
  • ytree 1.97 – file manager for file and archives.

Slitaz armhf comes with tazpkg package manager which allows to install packages just like you would do with apt-get in Raspbian. There are over 3,300 packages available for Slitaz (x86), and for now, over 250 packages are available for Slitaz armhf.

Let’s get try it out. First, download slitaz-armhf-mini-2012-12-14.zip, extract it, and copy it to an SD card (512 MB or greater) with Win32DiskImager (Windows) or dd (Linux). Insert the SD card in the Raspberry Pi, and within a few seconds the system should boot. From power to login prompt, it takes about 18 seconds, and the kernel takes  3 to 5 seconds of this time.

Dropbear is not running by default, so you’ll have to start it, if you want to login via SSH:


To start dropbear at boot time, edit /etc/rcS.conf, and add dropbear to RUN_DAEMONS (RUN_DAEMONS=”dropbear”).

Now let’s check the kernel version, as well as disk and memory usage.

Slitaz kernel version, SD card and RAM usage in Raspberry Pi

Let’s now try a few command with tazpkg, Slitaz package manager .

To list installed packages:


To list packages on the mirror:


Finally to install a package (e.g. file utility):


More commands and option are available on tazpkg manpage.

Although Slitaz (x86) is based on LXDE and Openbox, LXDE can’t be installed in Slitaz armhf with tazpkg as the required packages have not been built. However, if some packages are missing,  you can always build them yourself using Slitaz Cookutils. There are 2 main components in Cookutils:

  • Cook lets you compile and create a package, provide a log file and check the receipt/package quality.
  • The Cooker is a build bot with more automation and can be used as a frontend to cook since it provides a CGI/web interface which lets you view cook logs in a nice and colored way.

To get started, you’ll first need to checkout Slitaz Developers Tools and the Cookutils from mercurial repositories:


For Slitaz armhf, you’ll also need to install Slitaz armhf toolchain, or build it yourself. Alanyih, the developer behind Slitaz arm port, also posted further “instructions” on Slitaz forums.

Support CNX Software - Donate via PayPal or become a Patron on Patreon
Subscribe
Notify of
guest
22 Comments
oldest
newest most voted
onebir
onebir
7 years ago

“openwrt is said to has a 3.3MB memory footprint, but Slitaz armhf comes with tazpkg package manager which allows to install packages just like you would do with apt-get in Raspbian.”
OpenWrt has a package manager too – opkg. It’s quite flexible (eg you can install packages to a USB disk, if your router or whatever has one). I’m not sure how the variety of packages in the repo compares tho, given OpenWrt’s target devices.

onebir
onebir
7 years ago


Ah – well that’s a good point. I’ve only used OpenWrt on a WR703N (& that only a little bit), so I didn’t know that…

Albert
Albert
7 years ago

I really hate “Read more” links. Please, show full posts on the home page!

TheCageybee
TheCageybee
7 years ago

@Albert +1.
Preferred the old style.
Are you trying to save bandwidth?

Albert
Albert
7 years ago

Install a sitemap plugin for WP and register on Google Analytics to see what you can improve.

lwill
lwill
7 years ago

I got this from my hosting company: Recently, we have noticed something strange. It turns out that some WordPress hosting sites are not being indexed by search engines. This applies only to recently launched websites running the latest stable WordPress release – 3.4.2. As it turns out, WordPress 3.4.2, by default, asks search engines not to index your website. To change this, log in to the WordPress admin area, go to Settings -> Privacy, select “Allow search engines to index this site” and click the Save Changes button. After this, your website will be visible to search engines. Again, this… Read more »

Peter Steenbergen
7 years ago

You really need to take a look at your SEO.
1) Change your perma links to custom and use (/%postname%/)
2) Use a plugin “WordPress SEO” from Joost de Valk (improves google readability and ranking)
3) Use the plugin “SEO smart links” (improves internal links automatically)

cnxsoft
7 years ago

@lwill Thanks I don’t think I have problems with being indexed, but it’s just much slower than last year. @Peter Steenbergen Do you mean you don’t see permalinks when you access my site? I’ll try the SEO plugins in a week or so. I make changes one step at a time and see the effects. The main problem with other sites showing before mine, is mostly probably because of the slow indexing. When I publish a post, I can see Google Bot visits my post within a few seconds, but it will only show up several hours later in the… Read more »

Peter Steenbergen
7 years ago


I do see permalinks, but they consists of the year/month/day/ format which google doesn’t like.

Secondly, sudden drops is most likely because of google changing stuff, not you. SEO is the keyword. Get the proper plugins and write the article with SEO in mind. (keyword density, placement amd such)

mornwrt
mornwrt
7 years ago

Raspberry pi + openwrt works fine
best distribution ever but you have to build you one image with the buildroot env…. than it will work !
Its to fast for sf its hf!
We need to port rpi-update to openwrt would be great;-)

Paco
Paco
7 years ago

Good job! Thanks for your work. The slitaz image boots fast and is really small.

To put it on a 256MB SD-Card: I first copied it to bigger card (dd), resized it there (gparted) and copied back to my computer giving be a smaller image.

What is the easiest solution to get the GPIO-pins running? There is http://code.google.com/p/raspberry-gpio-python/, but the precompiled binaries are for raspian.

alanyih
alanyih
7 years ago

cnxsoft : @Paco Since raspberry-gpio-python C source is available, you’d just need to build it. ImportError: No module named zlib 1. python-pip help> modules pip Here is a list of matching modules. Enter any module name to get more help. pipes – Conversion pipeline templates. popen2 – Spawn a command with pipes to its stdin, stdout, and optionally stderr. test.test_pipes pip help> pip problem in pip – : No module named zlib 2. pip $ pip –help Traceback (most recent call last): File “/usr/bin/pip”, line 8, in load_entry_point(‘pip==1.2.1’, ‘console_scripts’, ‘pip’)() File “/usr/lib/python2.7/site-packages/pkg_resources.py”, line 318, in load_entry_point return get_distribution(dist).load_entry_point(group, name) File… Read more »

Matt
5 years ago

Is this project still maintained?

Advertisements