It will be nice a port for our N900

Here's an interesting pdf from AI where they explain that Super Jumbo is an application of the chroot technique:
http://elinux.org/images/5/5c/ELC-Al...ing-Gentil.pdf

I should not distrub you guys. But I have a question. Isnt there any simple way to put all os in bootmenu? like you give me the link I download and reboot and there I see options from 1 to 9. I have nitroid kernel-power and kernel-simple one I see all three options in bootmenu and all three workfine

Boot menu - just install these using ubuntu guide and nitdroid. Use multiboot.

This is great as it's boots the selections from UBOOT; which we need in order to use Meego....

I was unable to get it to extract Correctly. I will try again..

@ Bun yes. Essentially it's just: partition SD, extract - boot.

Edit: @ Debernardis: I will try and extract again now. I have seen posts that it's works on BB RevC (4) which is the 600-720mhz Beagle.

Edit 2: This damn thing. Tried extracting again. Caused my partition to die again.
I'm going to try one more time on my mac (VM) and if it fails, I will re download tomorrow.
Trying for a 4th time now under a VM.

Edit 3: Always makes my SD "Unrecognisable Partition".. What the hell!?


IDEA! Bloody linux! extract it from the tbz2 to super-jumbo.a and then dd the *.a

The .a file is a partition table. (Magic numbers are helpful.) If you want to extract anything you need to mount it with offsets.
That's easier than using dd.
This is the identity i get:
ai-superjumbo-2011-03.a: x86 boot sector; partition 1: ID=0xc, active, starthead 1, startsector 63, 1493982 sectors; partition 2: ID=0x83, starthead 0, startsector 1494045, 5108670 sectors; partition 3: ID=0x82, starthead 0, startsector 6602715, 996030 sectors, code offset 0x0
Whole partition table right there.
I did this:
Found the offset, which is start sector multiplied by 512. (in this case, use 764951040 as offset. It will give you the second partition, which is storage. The third is swap, and the first is the boot sector.)
I mounted it with offset and loop as options.
I got the contents.
So, here we have some .squashfs files. Same as on a regular live-cd. I guess they're easy to mount and use.
So, yeah. That's all you can do with the image. :P

Look carefully in the partiton. The files are hidden, and the OSs aren't whole. The .overlay folders contain files that are needed for the systems to work.
I also believe that the images are compatible with PowerVR SGXs.
Only thing i haven't found yet is the kernel.

I've made images from them. Ready to use.

This would be great if one could use it o a daily basis.

This is nice ...

does this mean that android's dalvik can run on a standard kernel or can a android kernel run a regular distro (full X11 libc etc) ?

Nokia 5700 - I'm so confused!! No clue what all that means!! Time for some google-fu!!

Will using dd work?
Any chance you can make it idiot proof for me? just drop in all the commands you used? I've never come up to a *.a file, yet.

The kernel should be in any/all of the OS in location /boot/

That's where I get all my beagle kernels from when trying a new distro.

Ok, i'll take it slow... :P
First, you get the file, right?
It's a tbz2 so extract it. The .a extension doesn't mean anything. It confused File-roller as well.
Look at the .a file as a .raw file.
But for this, to mount it, you need a Linux installation with mount. You do have that, right?
These are the commands:
That will mount it, and expose all the files in the image. So, let's get the files. The folders are hidden, so you want to show them. (In xterm, it doesn't matter. Just use ls -a.)
Most of the folders are self-explanatory. the .overlay-* folders contain some data. Dunno what it's for, though. (Possibly for using a "mount --bind" command.)
Search for the .squashfs-files. They contain the OSs, and you can easily mount them without selecting filesystem. (Of course, you need loop.)
Like this:
Most preferably you'd extract the images from the file before mounting.
The squashfs files aren't directly usable by N900. They need to be put over into a new container, like a .img.ext3 file. (I did so.)
That will make them usable for chroots and etc.
What more do you need to know about the process?

Sadly, my N900 isn't up for chroots... It's stuck with browerd atm... -.-'

debernardis already pointed it out, and the source also doesn't lie:
http://git.alwaysinnovating.com/cgit...leos/switch.sh

It is just several chroots, which you can already do using Easy Debian. If anything, the hard part comes from having a single kernel that can run both Android stuff and a normal GNU userspace, something that there's little chance it is directly portable to the N900.