OESF Portables Forum

Everything Else => Zaurus Distro Support and Discussion => Distros, Development, and Model Specific Forums => Archived Forums => Sharp ROMs => Topic started by: craigtyson on March 05, 2005, 06:36:43 pm

Title: Cacko Rom Install Via Network
Post by: craigtyson on March 05, 2005, 06:36:43 pm

Have installed several packages via network and while all have installed most have not worked.  I am now copying ipks to SD and all work fine.

Anyone having similar problems with apps try copying the ipkg to local storage before installing

Might be worth putting on the cacko faq?

Title: Cacko Rom Install Via Network
Post by: stupkid on March 06, 2005, 03:35:06 am

I've only noticed this with very large installs and then only with qinstall the graphical installer.  Using the command line ipkg is more reliable in my experience.

Title: Cacko Rom Install Via Network
Post by: craigtyson on March 06, 2005, 06:15:49 am

Its definatly worth a mention somwhere though  Im now on reflash no 3 and shedloads of time playing tyring to get apps to work...  Even managed to break hancom word by "reinstalling" it from the gui from network. On secont thoughts I'm now alot more familiar with cacko and my 750........

So did someone say gimp works on cacko? .......

Title: Cacko Rom Install Via Network
Post by: stupkid on March 07, 2005, 10:33:21 am

Yeah GIMP is in the feed as xqt-gimp.  It is an X app hence the naming.  

I have not been able to get consistent behaviour with network installs breaking for me to properly test.  The only time I have had problems is the first attempt after a fresh ROM install.  If I could get consistent behaviour I would be able to fix, but I actually use my Z so I haven't tested it thoroughly.  I will when we start working on a new ROM.

Title: Cacko Rom Install Via Network
Post by: iamasmith on March 07, 2005, 10:41:24 am

Perhaps the larger apps are failing due to depletion of /dev/shm which is set to 10m and where /tmp resides (actually symlinked to /dev/shm/tmp)?

I'm assuming that the Add/Remove Software tool utilises /tmp as a download location for the IPK and then possibly does a first pass unpack into /tmp before transferring to the target location (extract control.tar.gz, data.tar.gz and then CONTROL from control.tar.gz)... haven't looked in great detail  at this but if that is the case then that would explain why you have better luck with packages which are downloaded and then installed..

Which apps are failing? big ones like perl?

Also I suppose it is feasible that the installer downloads everything and batches the installs... not sure if this is the case but it would certainly account for a more rapid depletion of tmp space if you selected multiple apps for network install and this was the case.