Re: bluetooth connection

Hi Marcus,

Nice to hear from you again!

>The idea being that the rootfs is a compressed (jjfs?)
>image on CF (seems faster in Ipaq File Store though), with
>an upper layer(for updates) going to an"incremental loopback
>image" over bluetooth/nfs to the linux bridge/server. I
>imagine it would also be possible to put another layer above
>which is built in ram to reduce bluetooth traffic (delayed
>caching?).
>Is this overcomplicating everything (heh)?
>
>
That's right it sounds a bit complicated. It may be easier to explain
with graphics.
I think I've heard about writable filesystems based on a read-only
medium + some ram for changes, but I didn't manage to find any
references yet...

>ps: at what stage is Haret wiping ram? Is it possible to
>image the ram to (say) CF before linux boots, and restore on
>or after reboot?
>
>
Yes. Just backup the ram before running HaRET and restore it after
reboot. However, we'd need a special tool to do it. This shouldn't be
too difficult to implement for someone familiar with PocketPC. By the
way, proprietary solutions exist (see
http://www.pocketpcmag.com/_archives/jul03/protect_data.asp for example).

Of course, this could/should be implemented in our future bootloader
too.That should be pretty easy for this program (which will have to
support vfat and pcmcia) to backup and compress the WinCE ram to cf
before booting Linux and restore it before booting WinCE. Anyway, we'd
need to figure out which part of the RAM needs copying and which part
doesn't (and can be used by the bootloader itself).

Cheers,

    Michael.

-- 
Michael Opdenacker
http://free-electrons.com