Other Help Topics :: HOWTO for creating .uci extensions?

Thanks to unionfs I found it very easy to get acroread 7 in DSL :

- in a chroot apt-get acroread (after pointing to the Marillat repositories in /etc/apt/sources.list)
- deb2dsl
- unpack the dsl extension in /opt/acroread
- mkisofs -R -hide-rr acroread | create_compressed_fs - 65536 > /cdrom/optional/acroread.uci

This extension is then loaded in the sytem with the unionctl command. I tried it with a fat PDF 1.6 document I have never seen it so fast ! I think this should be a main option for creating extensions in the future because it's so easy and quick, and it's very ram friendly.

Quote (mikshaw @ May 03 2006,21:22)

There is some stuff in the wiki
http://damnsmalllinux.org/wiki/index.php/Category:MyDSL

Ideally I suppose there could be more info, but writing docs is no fun =o)

The building of .uci extensions is clear to me now. With 2.4 supporting 64 cloops I suppose these will become more popular. My first test will probably be to create a flock .uci.

Thanks bunches for the link! The docs are spread out, as you know, and probably could be better organized.

clacker, thanks. I've got it (I think!) and can go from here. Your explanation (which is truly excellent, BTW) should really be copied into the wiki.

Quote (clacker @ May 05 2006,18:08)

I thought it might have been because *.tar.gz extensions were supposed to be safer that the regular dsl ones, but apparently there isn't a check for that.

I'd say tar.gz and uci are "safer" than dsl, simply because they don't access most of the base system. However, these safer packages can still easily cause the complete destruction of your OS if created by a malicious fiend and not checked by the user. For example, bootlocal.sh could be replaced by something that causes lots of damage next time you boot. Or more immediately, .bashrc could be replaced by a different script that would run the next time you opened bash. Poof, there goes all your data.

original here.