October 11th, 2006 by
danielkMaemo 2.0 requires the legacy Scratchbox 0.9.8 which does not support the amd64 architecture natively. However, I’m running Ubuntu on amd64 and managed to get Scratchbox working inside a 32-bit chroot environment. Scratchbox itself is built around chroot, so this approach has the weird consequence that I’m now running two nested chroot environments — like matryoshki.
In order to save others the hassle of figuring out how to set this up (read: Murray extorted it from me), I put together a little howto on the subject. Enjoy!
Murray Cumming says:
October 17th, 2006 at 13:40
So what’s all that K86*, S94*, K85*, S95* stuff about?
danielk says:
October 17th, 2006 at 15:03
When SysV init makes a transition from one runlevel to another, it runs the init scripts linked to from the appropriate /etc/rc?.d directory. The names of the links put there to start a service are prefixed with “S” whereas those intented to stop a running service have the “K” prefix. The two-digit number that follows then defines the order in which the various scripts are executed, since often an initialization task depends on something else having already been initialized.
The particular values I chose in this howto just happened to fit somewhere in between. Of course this is highly system-dependent, thus I cannot say for sure whether the same numbers are going to work on Debian, for instance.
An interesting side note: Ubuntu is developing a replacement for SysV init called upstart, to be included with Edgy Eft. Apart from being asynchronous, this will presumably make the whole system initializiation business much more sanely configurable and less error-prone.
danielk says:
October 23rd, 2006 at 16:01
As it happens I just stumbled upon
update-rc.d, a tool shipped with Debian and derived distributions for use by package installation scripts. I have updated the howto to make use ofupdate-rc.d, as this makes the runlevel linking bit look a lot less threatening.