Re: [coLinux-users] installing distro that uses cramfs for initrd

[Henry N. <Hen...@Ar...>]

Luis Lavena wrote:
> On Mon, Apr 28, 2008 at 7:28 PM, Henry Nestler <Hen...@ar...> wrote:
>> Luis Lavena wrote:
>>  > Thank you Jason for your answer, but the thing is that the kernel that
>>  > cames with coLinux is not possible to mount cromfs/cramfs, even on a
>>  > pre-installed distro like ubuntu using a loop device to extract the
>>  > initrd contents of the CD.
>>  >
>>  > If you look at my configuration file, you will see that I'm not trying
>>  > to boot from that, but just using as root, which seems not to work.
>>  >
>>  > In any case, I'll try a full boot with that distro and maybe convert
>>  > it to another format.
>>
>>  Try this, there crams is enabled:
>>  http://www.henrynestler.com/colinux/testing/devel-0.8.0/20080428-cramfs/
>>
> 
> Thank you Henry, that actually made me get one step further...
> 
> Now I'm getting something like this, since it appears the file system
> of the initrd is readonly and coLinux initrd is not able to create the
> lib directory. into defined root...
> 
> Installing modules for coLinux 2.6.22.18-co-0.8.0-SVN1038

Oh, sorry. I putted some wrong. Kernel and modules are not from same
build. But, does no matter for your problem, the kernel file was ok.
File uploaded as "modules-2.6.22.18-co-0.8.0-SVN1038-20080428.tgz" now.

> Mounting cofs for vmlinux-modules.tar.gz
> tar: Cannot create directory `lib/': Read-only file system
> tar: Cannot create directory `lib/': Read-only file system
> tar: Cannot create directory `lib/': Read-only file system
> tar: Cannot create directory `lib/': Read-only file system
> tar: Cannot create directory `lib/': Read-only file system
> tar: Cannot create directory `lib/': Read-only file system
> tar: lib/modules/2.6.22.18-co-0.8.0/kernel/arch/i386/crypto/aes-i586.ko: No such
>  file or directory
> Closing /

The messages above are from coLinux "initrd=intrd.gz", that is normal
for cramfs.

> VFS: Mounted root (cramfs filesystem) readonly.
> Trying to move old root to /initrd ... /initrd does not exist. Ignored.
> Unmounting old root
> Trying to free ramdisk memory ... okay
> Freeing unused kernel memory: 140k freed
> 
> That was from the colinux console, this is from -v 3:
> 
> RAMDISK: Compressed image found at block 0
> VFS: Mounted root (ext2 filesystem).
> ReiserFS: cobd3: warning: sh-2021: reiserfs_fill_super: can not find reiserfs on
>  cobd3
> VFS: Can't find ext3 filesystem on dev cobd3.
> VFS: Can't find an ext2 filesystem on dev cobd3.
> VFS: Mounted root (cramfs filesystem) readonly.

Don't use the initrd.gz from coLinux. This tries to intstall modules in
your cramfs. Cramfs is read only all times.
If you needs modules at some install point later, then install it
manualy with a mount over "cofs0".

You should use only the initrd from Distry for installing. I don't know
how you can stop from installing the distro kernel. For installing the
coLinux kernel you properly needs some hacks in the initrd, look arround
the coLinux-Knoppix boot...

-- 
Henry N.