{"id":55,"date":"2009-10-04T11:15:00","date_gmt":"2009-10-04T09:15:00","guid":{"rendered":"http:\/\/www.hauweele.net\/~gawen\/blog\/?p=55"},"modified":"2014-05-12T19:44:24","modified_gmt":"2014-05-12T17:44:24","slug":"howto-save-a-lot-of-disk-space-on-nokia-n810","status":"publish","type":"post","link":"https:\/\/hauweele.net\/~gawen\/blog\/?p=55","title":{"rendered":"Howto save a lot of disk space on nokia N810"},"content":{"rendered":"

The Nokia N810 is an internet tablet (not a phone though it can communicate with cellular phone via bluetooth). It’s a nice small device which run the Maemo Distribution<\/span> which seems to be based on Debian<\/span> since it uses the Debian Package Manager. But the distribution’s structure really feels like an embedded device and this is quite annoying when you try to optimize this device.
One thing which is really boring is the lack of disk space on the device. Actually the device use two miniSD (MMC) cards for personnal documents, images, videos and so on and a 256MB MTD using a JFFS2 compressed file system to store the whole distribution which means every package and their data files which takes a large amount of disk space and even so much that the MTD can easily be completely filled with a few apps.
The basic idea to save some disk space is to move some part of the MTD on the MMC primarely reformated from vfat<\/span> to ext2<\/span>. Many articles explain how to move stuff like \/var\/cache <\/span>and others using symlinks which can save you about 20MB. But they also explain that you can’t do that with \/usr\/share\/<\/span> for example since it will break the boot process. Indeed the boot process depends on many stuff located in \/usr\/share<\/span> and thus if the MMC are not mounted while boot occurs the system will just stall waiting for an hard reset to get everything right and clean again. Here comes a way to go around this :<\/p>\n

As root we check the run level :<\/p>\n

Nokia-N810-43-7:~# runlevel<\/span>
N 2<\/span><\/span><\/p><\/blockquote>\n

<\/span><\/span>We see we are in runlevel 2. Let’s check how the boot process arranges itself in that runlevel :
<\/span><\/span><\/p>\n

Nokia-N810-43-7:~# ls \/etc\/rc2.d<\/span>
K00zzinitdone<\/span>
S12fb-progress.sh<\/span>
S20dbus<\/span>
S20hal<\/span>
S20osso-applet-display<\/span>
S21mce<\/span>
(…)<\/span><\/span><\/p><\/blockquote>\n

It looks like fb-progress.sh <\/span>is the first script executed in the boot process.<\/span> So we edit this script (\/etc\/init.d\/fb-progress.sh<\/span>) and add the following line at the beginning of the script (line 19 or so):<\/p>\n

\/usr\/sbin\/osso-mmc-mount.sh \/dev\/mmcblk0p1 \/media\/mmc2<\/span>
\/usr\/sbin\/osso-mmc-mount.sh \/dev\/mmcblk1p1 \/media\/mmc1<\/span><\/span><\/p><\/blockquote>\n

So we know that MMC will be mounted at first in the boot process. After that scripts which need share <\/span>stuff or other may look on the MMC since we know they were already mounted. Then we move things like \/usr\/share<\/span> on the MMC :
<\/span><\/span><\/p>\n

Nokia-N810-43-7:~# mkdir \/media\/mmc1\/.usr<\/span>
Nokia-N810-43-7:~# cp -aR \/usr\/share \/media\/mmc1\/.usr<\/span>
Nokia-N810-43-7:~# rm -rf \/usr\/share
Nokia-N810-43-7:~# ln -s \/media\/mmc1\/.usr\/share \/usr\/share<\/span><\/span><\/p><\/blockquote>\n

Of course the same could be done for other directory. Here is the list of directory that I switched from MTD to MMC without breaking the boot process :<\/p>\n