site  contact  subhomenews

Wary 093 works on Gecko Edubook

October 27, 2010 — BarryK
Well, kind of. I booted the Gecko from a USB stick and got a desktop with the 'rdc' X driver. Got the "woof woof". Clicked the 'connect' icon and was online with wireless. Wow, that's great!

Oh yeah, I should also mention that it powered-off when I shutdown. That was a troublesome thing before.

So, very good, but the bad news is that SeaMonkey crashed at startup with "illegal instruction". I compiled SM for a 486 CPU, ah, but maybe the Flash plugin crashed and that would have brought down the browser. I'm not running it now, so can't check that.

Two pkgs that I had compiled for a 686 CPU are libvpx and ffmpeg, so they would need to be recompiled.

So, apart from the issues of the CPU not being quite a 686, this Wary looks good on the Gecko. Someone with a Gecko could take this on as a project if they like, to recompile whatever apps crash, maybe use an older Flash player.

Note that Wary 093 is not yet released. It has the 2.6.31.14 kernel. It should be out in a couple of days.

Comments

wary 5 on gecko
Username: pskin
Hi Barry, I managed to compile libvpx and ffmpeg for the Gecko, and found that the latest flash plugin from Adobe seems to work. So I hope to bring out a gecko edition soon, once I have tested a bit more. I also compiled mplayer and mencoder, and they worked very well, but had rather large binaries (11M for mplayer). I saw that mplayer has a large overlap with ffmpeg, but could not find a way for mplayer to share the libraries, so gave up. I guess that appropriate configure options to leave out unused features might reduce the size, and I'd be grateful for suggestions from anyone with experience at this. Do you think it is better to include mplayer in the gecko edition of wary 5 or keep it separate as a pet? (Technosaurus pointed me to his very clear instructions on making pets).

wary 5 on gecko
Username: pskin
"Hi Barry, I managed to compile libvpx and ffmpeg for the Gecko, and found that the latest flash plugin from Adobe seems to work. So I hope to bring out a gecko edition soon, once I have tested a bit more. I also compiled mplayer and mencoder, and they worked very well, but had rather large binaries (11M for mplayer). I saw that mplayer has a large overlap with ffmpeg, but could not find a way for mplayer to share the libraries, so gave up. I guess that appropriate configure options to leave out unused features might reduce the size, and I'd be grateful for suggestions from anyone with experience at this. Do you think it is better to include mplayer in the gecko edition of wary 5 or keep it separate as a pet? (Technosaurus pointed me to his very clear instructions on making pets).

mplayer and ffmpeg
Username: BarryK
"Replied here: http://bkhome.org/archive/blog2/201101/compiling-mplayer-and-ffmpeg.html


Tags: wary