Re: Re: copy-on-write solution

>> We could even load the bootstrap-image into memory using cramfs, thus
>> eliminating the need for the CF-card to stay in the slot.
>
> This is interesting idea. Would this be accomplish through small
> initrd like
> we have now for CF/NFS boot? Anyway, instead of cramfs filesystem
> squashfs
> filesystem can be used. It has better compression ratio (almost 10%).
> So, based on your suggestion my idea is to copy compressed filesystem
> (cramfs, squashfs, cloop or something else) from CF card to ramfs and
> mount
> it either through a ramdisk device or through the loopback filesystem.
> Over
> this block device than cowloop driver is mounted to divert writes
> again to
> ramfs. What do you think? What are the latest CFboot images to work
> with?
> Are tthis on http://handhelds.org/~koen/CFrootfs/ ok?

I don't really have an idea how it would exactly work, but your idea is
probably the best solution. You can use the images found in
http://handhelds.org/~koen/OE-images/ . They just need to be adjusted
according to the guide in
http://www.handhelds.org/moin/moin.cgi/HpIpaqH2200CFBoot . Chris Larson
is working on making initrds with OE, but for now we have to make them
manually. I've noticed that 2.6.8.1 has some problems with the pcmcia
drivers compiled in, so we probably need a 4M initrd to include that
modules.

regards,

Koen
Received on Wed Sep 15 12:52:13 2004