(kernel 2.6.26 released, 2.6.33.5 as snapshot) |
(→Kernel Version: - updated to reflect 0.7.8 should work) |
||
| (2 intermediate revisions by 2 users not shown) | |||
| Line 2: | Line 2: | ||
== Kernel Version == |
== Kernel Version == |
||
| − | The ''mountall ''program used in Ubuntu Karmic uses ''/proc/self/mountinfo'' to ensure partitions are mounted properly. This file has been [http://kernelnewbies.org/Linux_2_6_26 introduced] by the linux kernel version 2.6.26. Therefore Ubuntu Karmic is not compatible with coLinux versions 0.7. |
+ | The ''mountall ''program used in Ubuntu Karmic uses ''/proc/self/mountinfo'' to ensure partitions are mounted properly. This file has been [http://kernelnewbies.org/Linux_2_6_26 introduced] by the linux kernel version 2.6.26. Therefore Ubuntu Karmic is not compatible with coLinux versions prior to 0.7.8. |
=== coLinux kernel 2.6.26.8 === |
=== coLinux kernel 2.6.26.8 === |
||
Thanks to the coLinux mailing list I discovered that there is an experimental coLinux kernel for download. According to the author, this kernel is widely untested, but seems to run quite well. The mountinfo issue disappears, the new modules are installed into the Karmic file system, but then the boot process hangs. This issue seems to be missing ''squashfs ''support in the kernel binaries (although ''squashfs ''is provided as a module), which is essential to access the initial ramdisk of Ubuntu Karmic. |
Thanks to the coLinux mailing list I discovered that there is an experimental coLinux kernel for download. According to the author, this kernel is widely untested, but seems to run quite well. The mountinfo issue disappears, the new modules are installed into the Karmic file system, but then the boot process hangs. This issue seems to be missing ''squashfs ''support in the kernel binaries (although ''squashfs ''is provided as a module), which is essential to access the initial ramdisk of Ubuntu Karmic. |
||
| − | * coLinux with kernel 2.6.26.8 is released and available on [http://sourceforge.net/projects/colinux/files SourceForge] now |
+ | * coLinux version 0.7.7 with kernel 2.6.26.8 is released and available on [http://sourceforge.net/projects/colinux/files SourceForge] now |
| − | === |
+ | === coLinux kernel 2.6.33 === |
| − | + | * coLinux 0.7.8 containing kernel 2.6.33.5 should be able to run Karmic |
|
| + | * You can build your own disk image using the instructions from[[Cobootstrap| Cobootstrap]]. |
||
| − | * coLinux with kernel 2.6.33.5 is available from [http://www.colinux.org/snapshots/ Snapshots] of branch devel now |
||
| − | * A [http://uni.goeb.org/pub/colinux-ubuntu-karmic.zip disk image] (177 MB) that runs with the 20100207 version is available for testing. It was built using an adapted version of the instructions from[[Cobootstrap| Cobootstrap]]. |
||
[[Category:Ubuntu]] |
[[Category:Ubuntu]] |
||
[[Category:Distributions]] |
[[Category:Distributions]] |
||
Latest revision as of 15:10, 22 February 2011
This page should be used to collect information on how to use the current Ubuntu version 9.10 Karmic Koala with coLinux.
Kernel Version[]
The mountall program used in Ubuntu Karmic uses /proc/self/mountinfo to ensure partitions are mounted properly. This file has been introduced by the linux kernel version 2.6.26. Therefore Ubuntu Karmic is not compatible with coLinux versions prior to 0.7.8.
coLinux kernel 2.6.26.8[]
Thanks to the coLinux mailing list I discovered that there is an experimental coLinux kernel for download. According to the author, this kernel is widely untested, but seems to run quite well. The mountinfo issue disappears, the new modules are installed into the Karmic file system, but then the boot process hangs. This issue seems to be missing squashfs support in the kernel binaries (although squashfs is provided as a module), which is essential to access the initial ramdisk of Ubuntu Karmic.
- coLinux version 0.7.7 with kernel 2.6.26.8 is released and available on SourceForge now
coLinux kernel 2.6.33[]
- coLinux 0.7.8 containing kernel 2.6.33.5 should be able to run Karmic
- You can build your own disk image using the instructions from Cobootstrap.