Re: Angstrom-Opie install on h2200 - and now?

On Sat, 20 Oct 2007, Gerhard Zintel wrote:
> This bug exists also for the Opie 1.2.1 version from the last Familiar
> release. I was very surprised that such a bug was not fixed or at least
> noticed much earlier. As often as I have to copy files I have to go into
> command line. And that without keyboard. A file manager in a PDA must be
> able to move and copy files in my opinion.

I have no argument with you there, it should definitely work. However, I just
tested again on my h3970 running self-built Familiar + Opie 1.2.1 and it
works fine, so there is a little more to this issue than you suggest. In any
case I will investigate.

> Is the development of Opie for Familiar canceled?

Opie development is still going on. As for Familiar, well, you'd have to ask
them yourself as they don't make public statements about their progress, and
I know for whatever reason they don't use OE anymore. Building Angstrom +
Opie images using OE is the only way to get up-to-date builds of Opie on
handheld devices right now.

> I read that there is still no support for Opie within the Angstrom
> distribution?! I don't get an overview about that subject.

That's because the majority of the guys involved in Angstrom don't use Opie
and don't care about it, so others of us have to push it through and make it
work.

> BTW: You gave me a link of your Angstrom / Opie built and it hasen't worked
> for me. From your local.conf file I just realized that you are compiling
> for jffs2 file system where I am using a CF-Card install with ext2 file
> system. Could that be the problem? I do not realy know the use of the jffs2
> file system.

I did specify to build jffs2 images but I do not use them. If you have a look
at my local.conf again you will see I am also building tar images. The image
I uploaded was a bz2 compressed tar image which is ready for extraction (as
root) onto an ext2 formatted CF card, and it definitely does work because I
have run that very same image on my own h2210 :) All you need in addition is
to place a correctly formatted "labrun" file into /boot on the card, and it
should boot OK (assuming you are using lab on your device).

Cheers,
Paul
Received on Fri Oct 19 2007 - 19:00:14 EDT