Tiny Core Linux

[Gerrelt]

Thank you bmarkus! I will check out the raspberry forum on tinycorelinux.

[bmarkus]

Updated wpa_supplicant.tcz, missing drivers added. Try and let us know the result at http://forum.tinycorelinux.net/index.ph ... 491.0.html

[bmarkus]

New piCore-X beta image available. It is compatible with both the 256M and 512M RAM boards:

http://www.hasix.org/tc/piCore-X-beta130114a.img.xz

[bmarkus]

New version of piCore-X available:

http://www.hasix.org/tc/piCore-X-beta130116a.img.gz

flwm_topside.tcz updated to be compatible with WM/DE extensions.

[bmarkus]

piCore updated to 4.7.4 base.

Visit Tiny Core Linux download page to get it:

http://tinycorelinux.net/ports.html

There is a new piCore-X image with 4.7.4 base, preinstalled graphical environment is unchanged. Download link:

http://www.tinycorelinux.net/4.x/armv6/ ... 24a.img.gz

[Gerrelt]

Thanx bmarkus, I've just installed 4.7.4 and it works great!

Greetings,

Gerrelt.

[bmarkus]

New image, piCore-X-beta130129a is available. Changes:

- Xorg-7.6.tcz updated, keyboard issues fixed

Download link:

http://www.tinycorelinux.net/4.x/armv6/ ... 29a.img.gz

[bmarkus]

piCore updated to 4.7.5 base. See announcement and download info

http://forum.tinycorelinux.net/index.ph ... l#msg85237

piCore-X beta is also updated, see

http://forum.tinycorelinux.net/index.ph ... l#msg85295

[bmarkus]

New piCore image dated 20130324 is now posted. It is a bug fix release adding missing gconv libs.

For download see: http://tinycorelinux.net/4.x/armv6/
Direct download: http://tinycorelinux.net/4.x/armv6/piCo ... 324.img.gz

Picore-X also updated. Direct download: http://tinycorelinux.net/4.x/armv6/piCo ... 324.img.gz

For more info visit http://forum.tinycorelinux.net/index.ph ... ,57.0.html

[bricolodu13]

Hello,

Following the Squeezelite post on Tiny Core, i would like to do the same "manually" to undestand what am I doing and do the same with GMediaRender.

My first problem is when I want to get Dropbear, I always get an error file "doesn't exist"
At the command promt
tce

s search
d Dropbear - choose the correct [16]
[16] Enter ----> wget: server returned error: HTTP/1.1 404 not found (tags.db.dropbear.tcz.info' : No such file or directory)

any idea ?

best regards,
Jean

[Forrrge]

This is looking good, anyone hear running it, thoughts on speed and performance ?

Looks as if its getting updated regular
http://forum.tinycorelinux.net/index.ph ... ,57.0.html

[Gerrelt]

I am still using Tinycore, now running piCore 5.0alpha6 on 3 Raspberries wireless as portable Squeezebox players.
Performance and speed is great. But I cannot judge on that, the player I use is very light (Squeezelite) and doesn't put much load on the system.

[Franxois]

I think piCore is great and should have more visiblility.

I just try to unmount and remove the sdcard and the raspberry is still running. Is there other OS who allow that ??

[jamesh]

I think piCore is great and should have more visiblility.

I just try to unmount and remove the sdcard and the raspberry is still running. Is there other OS who allow that ??

Yes, you can hot swap the SD card in Raspbian *I think*.

[jackokring]

Nice work! Now if only I could load up my eeepc driver for wifi to work with the working wpa_supplicant.

I think this distro is a nice compromise for custom software with small image downloads. It does have problems at present.
1) No wifi browser to find help by default.
2) No easy library for bit mapping a graphic array, and sound array.
3) A session use manager for say coding and gaming profiles, etc.
4) A tgz package builder.

Good points include
1) Session based commit to disk.
2) Low overheads on machine resources.
3) Fewer long term problems with static data.
2)

[visionimpaired]

I am trying Tiny Core and my pi does no automount or umount my USB memory stick (like hotswap).
Is there a trick to do to make this work?
Otherwise, I love the size - and the learning curve.
VI

[Gerrelt]

I didn't know how to either, but I think I figured it out now.

Most of this is taken from this post from bmarkus from the tinycore forum:
http://forum.tinycorelinux.net/index.ph ... l#msg52676

Login to piCore, and open this file:
(if nano not installed, execute first: tce-load -wi nano.tcz)

Code: Select all

sudo nano /etc/udev/rules.d/98-tc.rules

Change the "Add" and "Remove" lines so the file looks like this:

Code: Select all

KERNEL=="ram*", SUBSYSTEM=="block", GOTO="tc.rules_end"
KERNEL=="loop*", SUBSYSTEM=="block", GOTO="tc.rules_end"
ACTION=="add",          SUBSYSTEM=="block",     RUN+="/bin/sh -c '/usr/local/sbin/usbadd.sh %k'"
ACTION=="remove",       SUBSYSTEM=="block",     RUN+="/bin/sh -c '/usr/local/sbin/usbremove.sh %k'"
LABEL="tc.rules_end"

It now will call the shell scripts "usbadd.sh" and "usbremove.sh".

After editing, reload the rules:

Code: Select all

sudo udevadm control --reload-rules

You will have to create the two scripts as follows:

Code: Select all

sudo nano /usr/local/sbin/usbadd.sh

And add this to the file:

Code: Select all

#!/bin/sh
rebuildfstab
sleep 3
mount /dev/$1 /mnt/$1 

The next usbremove script:

Code: Select all

sudo nano /usr/local/sbin/usbremove.sh

Add this:

Code: Select all

#!/bin/sh
umount /mnt/$1
sleep 1
rmdir /mnt/$1
rebuildfstab

Now make the scripts executable:

Code: Select all

sudo chmod a+x /usr/local/sbin/usbadd.sh
sudo chmod a+x /usr/local/sbin/usbremove.sh

Now you will have to make the changes and file persistent, open this file:

Code: Select all

sudo nano /opt/.filetool.lst

And add these lines to the end of it:

Code: Select all

etc/udev/rules.d/98-tc.rules
usr/local/sbin/usbadd.sh
usr/local/sbin/usbremove.sh

And save it all:

Code: Select all

filetool.sh -b

Do a reboot.

If you now plug in a USB drive, it should be automatically loaded.
It will take a few seconds, but then the files should be available under: /mnt/sda1

BE AWARE: This will not mount the drive at startup!! Only if you plug it in after startup.

[bmarkus]

The cleanest way is what Gerrelt posted, using custom udev rule for automounting. For unmounting no real good solution if user removes the stick without explicitely unmounting it, a script can't protect against data loss.