View Single Post
Posts: 98 | Thanked: 142 times | Joined on Mar 2011
#49
Originally Posted by juiceme View Post
That was my original idea, but it seems not to be easy to do. I experimented quite a lot with the vanilla Nokia kernel, both to use kexec as module and as compiled-in feature but the results were not very good. With the Nemo kernel it is lot easier.

With this method I am using, all you need is to flash the first stage kernel just once, and any of the second-stage kernels can be booted from a directory in the filesystem.

You can have multiple kernels running on the same filesystem, just by starting them with a different command line; for example I have both the nitdroid kernel (running the normal way of chrooting it to /home/nitdroid/) and an own flavour of openmode Nokia kernel, either one can be launched from a file on the FS.

Also, as the selection is done before booting the final kernel I can rearrange partittions as I like, mounting for example Nemo partition as root and launching the Nemo kernel.

Nothing would prevent me running Debian, for example using my Harm-Chom-install image, mounting it as root and starting a kernel of my desire on it. (I could do that, but there is no point really as of course it would not use the phone functionality)
Out of curiosity have you looked into booting nemo via a chroot ala nitdroid? I briefly tried to get it to work that way, but at the time I was trying to make a single kernel that booted both Nitdroid and Nemo, but ran into some issues and lost interest. Your way of actually separating the kernels is a lot better, and I think not having to sacrifice a partition on the EMMC would be a better solution to running Nemo. You could basically add something like a real_root argument to the kernel command line, and the preinit script could take that and use it to determine where to chroot before running init.

Last edited by Sazpaimon; 2013-01-01 at 22:58.
 

The Following User Says Thank You to Sazpaimon For This Useful Post: