Messages

1

Angstrom & OpenZaurus / help with ipkg

« on: May 24, 2004, 10:22:36 pm »

Now that I\'ve let it rest a day:  even though it gives me all of those errors it does seem to copy and link the appropriate files in the correct places, but since it is giving the status write error would this keep it from realizing that the package was installed successfully since it can\'t record that.

So can I move all of the ipkg logs to ram and link them to where they normally are?

I was using AQpkg when I got the errors.  Yes \" ram  /mnt/ram\" is in the config file.  I did try using the command line with -d ram , but it generated the same results as the GUI.

Shouldn\'t other people be experiencing this problem?  Maybe I should just go for 3.2.

2

Angstrom & OpenZaurus / help with ipkg

« on: May 23, 2004, 03:28:33 pm »

I\'ve recently flashed 3.3.6pre1 on a 5500.  This is the first OZ I have used.  I chose the 40/24 image.  I use my zaurus for an MP3 player so I\'m trying to install mplayer and xmms.  I select \"install to ram\", but all I get are linking errors and it starts by trying to access /mnt/cf.   It also gives an error that it can\'t write the ipkg status file because there is no room.  Everything ends with a nice SIGSEV.  How do I fix all of this?  I want to install to ram because the space is there and I don\'t want to format my cards to ext2.  It isn\'t just mplayer; tximage doesn\'t install either.

Thanks for any help.  I just expected the packaging system to install one thing correctly.