Hentges Rom: New Versioning System

[CoreDump]

New images for SL-Cxx00 and Collie are online. There has been a typo in ipkg.conf (sigh), please
ipkg update / ipkg upgrade to install a hotfix.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=145175\"][{POST_SNAPBACK}][/a][/div]

Ah the joys of error-proofing. While the hotfix from above works nicely once installed, it does depend on a certain feed layout. Currently it prevents me from rsyncing the live-feed with my feed @ home  

I'll write a little script called "dist-upgrade" which only job it will be to upgrade the installation. It will be completely independent of /etc/ipkg.conf (ie: It will even work on badly damaged systems), it will be able to install ipkg-independent "hotfixes" and it will be hardened against most types of failure.

[CoreDump]

New images for SL-Cxx00 and Collie are online. There has been a typo in ipkg.conf (sigh), please
ipkg update / ipkg upgrade to install a hotfix.
[div align=\"right\"][{POST_SNAPBACK}][/a][/div]

Ah the joys of error-proofing. While the hotfix from above works nicely once installed, it does depend on a certain feed layout. Currently it prevents me from rsyncing the live-feed with my feed @ home  

I'll write a little script called "dist-upgrade" which only job it will be to upgrade the installation. It will be completely independent of /etc/ipkg.conf (ie: It will even work on badly damaged systems), it will be able to install ipkg-independent "hotfixes" and it will be hardened against most types of failure.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=145214\"][{POST_SNAPBACK}][/a][/div]

Please, everyone using the images from above download and install the dist-upgrade package for your machine:

EDIT: Updated packages:
[a href=\"http://oz.hentges.net/hentges-feeds/1.0.x/machine-upgrades/akita/dist-upgrade_0.0.2-r0_akita.ipk]http://oz.hentges.net/hentges-feeds/1.0.x/....2-r0_akita.ipk[/url]
http://oz.hentges.net/hentges-feeds/1.0.x/....2-r0_spitz.ipk
http://oz.hentges.net/hentges-feeds/1.0.x/...2-r0_collie.ipk


You can then upgrade your installation to 1.0.0-wip-20061101 by running "dist-upgrade" in a console.

[samac]

Coredump

I am a little confused. Before dist-upgrade feeds existed for .../1.0.x/common and machine upgrades, after dist upgrade they didn't.

Also .../3.5.4.1/feed/machine/collie does not exist.

Could you list the feeds that are relevant for each machine, are we meant to use the ../1.0.x/ or not?

samac

[Meanie]

Coredump

I am a little confused. Before dist-upgrade feeds existed for .../1.0.x/common and machine upgrades, after dist upgrade they didn't.

Also .../3.5.4.1/feed/machine/collie does not exist.

Could you list the feeds that are relevant for each machine, are we meant to use the ../1.0.x/ or not?

samac
[div align=\"right\"][a href=\"index.php?act=findpost&pid=145334\"][{POST_SNAPBACK}][/a][/div]

The clamshell models have OZ 3.5.4.1, the other older models have OZ 3.5.4.2

I am going to try the new hentges as soon as I get everything backed up.

[CoreDump]

Coredump

I am a little confused. Before dist-upgrade feeds existed for .../1.0.x/common and machine upgrades, after dist upgrade they didn't.

Also .../3.5.4.1/feed/machine/collie does not exist.

Could you list the feeds that are relevant for each machine, are we meant to use the ../1.0.x/ or not?

samac
[div align=\"right\"][a href=\"index.php?act=findpost&pid=145334\"][{POST_SNAPBACK}][/a][/div]

The hentges feeds are for distribution upgrades only. The "dist-upgrade" tool will always use the correct feeds, independent of ipkg.conf.

Adding the hentges feeds to ipkg.conf would be a waste of ressources (since ipkg is slow enough already)

[samac]

The hentges feeds are for distribution upgrades only. The "dist-upgrade" tool will always use the correct feeds, independent of ipkg.conf.

Adding the hentges feeds to ipkg.conf would be a waste of ressources (since ipkg is slow enough already)

OK that makes sense.

Thanks

Samac

[Hrw]

The clamshell models have OZ 3.5.4.1, the other older models have OZ 3.5.4.2[div align=\"right\"][a href=\"index.php?act=findpost&pid=145364\"][{POST_SNAPBACK}][/a][/div]

Collie latest is 3.5.4
clamshells latest is 3.5.4.1
poodle/tosa latest is 3.5.4.2

For collie I suggest using hentges version of OZ.

[CoreDump]

The clamshell models have OZ 3.5.4.1, the other older models have OZ 3.5.4.2[div align=\"right\"][a href=\"index.php?act=findpost&pid=145364\"][{POST_SNAPBACK}][/a][/div]

Collie latest is 3.5.4
clamshells latest is 3.5.4.1
poodle/tosa latest is 3.5.4.2

For collie I suggest using hentges version of OZ.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=145479\"][{POST_SNAPBACK}][/a][/div]

Maybe we should do a 3.5.5 for all devices? That way we don't have some devices bit-rotting away.

OTOH I belive that staged releases (3.5.4 = Collie, 3.5.4.1 = clamshells etc) are a very developer friendly way of doing things. One can sit down and concentrate on a specific model / series and make it release-ready, ignoring any other device completly.

The current problem I see is that
a) Only very few people are actively working on OpenZaurus directly
b ) Of those that do work on OZ, most would be happy to let SL-5x00 (ie: Collie and Poodle) die a silent death.

The a) part could only be helped by motivated and knowledgeable Linux users joining the project (and yes, installing and using OE is required)
The b ) part is a little bit more difficult.

Devs usually avoid SL-5x00 like the plaque because:
- The small rootfs (15-18Mb) make them a PITA to work with
- The screen is sub-standard and hard to read compared to the clamshells
- The screen is only QVGA (320x240)
- The keyboard is pretty bad compared to the clamshells

So on one hand we have many users still owning and using these devices, but OTOH we have very few devs that care about them.

Over the next few days, I'll convert Poodle to an SD-only rootfs. And with SD-only I mean SD-only. Hentges will no longer offer flash installations!. Poodles will get a tweaked kernel that boots the SD directly, and a tuned updater.sh which installs rootfs tarballs onto any inserted SD card (just like the spitz installer does for the MicroDrive).

If the above works out, it will make dev work a lot easier with Poodle since we no longer need to care about not-filling up the rootfs.

Why Poodle and not Collie? Simple: because Poodle is already running kernel 2.6.

[CoreDump]

Here's a shot of the new updater.sh I wrote for Poodle:

[img]http://hentges.net/tmp/screenshots/Zaurus/Poodle/Misc/updater-reloaded.jpg\" border=\"0\" class=\"linked-image\" /]

This version allows for root-on-sd which the old one could not handle.

[CoreDump]

The new Poodle SD images are online:
http://hentges.net/tmp/snapshots/Hentges-ROM/1.0.0/20061104/

The rootfs is installed onto the first partition of your SD card. You may repartition the card if you have a lot of space but partition one should not be smaller than 150Mb


Installation Instructions:
- Download a rootfs.tar.gz from the "tarballs" directory and rename it to sdimage1.tgz
- Download the kernel and rename it to zImage.bin (flashing the kernel is required)
- Copy the new updater.sh (an older one won't work!), gnu-tar , zImage.bin and sdimage1.tgz to a CF card
- Start the flashing process as usual.

Please keep in mind:
- updater.sh was written from scratch and may contain bugs. Please post about any problems during instalation.
- updater.sh (and thus the sdimage installer) runs under an ancient SHARP kernel 2.4. This kernel contains
a patch to disallow "async" SD/MMC access. Because of this the installation may take longer than 30 minutes! There is nothing I can do about this (short of replacing the updater mini-OS)
You may extract the rootfs tarball on partition one of your SD card manually (as root!) which can be a lot faster (depends on your distribution)
- The current GPE image needs some more love. It is basically a copy of the "spitz" clamshell GPE image (containing Firefox, xscreensaver etc). This was not intended and will be fixed eventually.

[Greg2]

- Copy the new updater.sh (an older one won't work!), zImage.bin and sdimage1.tgz to a CF card

and gnu-tar?

d/l'ing now

Thanks, CoreDump  

Greg

[CoreDump]

- Copy the new updater.sh (an older one won't work!), zImage.bin and sdimage1.tgz to a CF card

and gnu-tar?

d/l'ing now

Thanks, CoreDump  

Greg
[div align=\"right\"][a href=\"index.php?act=findpost&pid=145601\"][{POST_SNAPBACK}][/a][/div]

Indeed    Fixed!

[CoreDump]

I've updated the distro feeds, please run "dist-upgrade" from the console.

[ennui719]

Hi CoreDump,
  Thanks for the work on Poodle. I flashed this new image and I'm sure it works fine, but on first boot, I get the pop up asking me what I want to do with the detected SD card, but it is too big for the screen and is immovible. I can't seem to use the arrow keys or tab to get to the "OK" button to make it go away. Any ideas?

Thanks,
   ennui719

edit:  Oh I see you are already on this... see post https://www.oesf.org/forums/index.php?showtopic=21910

[samac]

I've updated the distro feeds, please run "dist-upgrade" from the console.

dist-upgrade works great, but I had a couple of problems.

1. The security module kept asking for the pin number whilst the upgrade was trying to calibrate, I eventually had to ssh in from my main box, remove security and reboot the collie.

2. dist-upgrade does not respect user alterations, it re-installed packages that I had removed, and it changed my decorative settings back to default.

samac