OESF Portables Forum
Model Specific Forums => Sharp Zaurus => Zaurus - pdaXrom => Topic started by: chiark on February 08, 2006, 06:17:25 am
-
I realise that pdaxrom is targeting experienced linux people as users, but unfortunately I am not one of 'em.
I've been struggling recently with a few things, such as library locations. If I choose to install something to /mnt/user using the package manager, the library will not be found after a reboot.
Changing /etc/ld.so.conf to add the path /mnt/user/usr/lib/ and then running ldconfig sorts this out.
Should this path be added to the baseline pdaxrom config?
Other things that would be useful would be a way of identifying where the space in the root partition has "gone" - knowing what are core OS files and what can be changed/removed would be good, as I find myself running out of space on / occasionally.
Is it possible to install man or info for pdaXrom? This would again help newbies such as myself...
I know these are newbie things, but it would help the learning curve.
-
For man, see development tools (https://www.oesf.org/forums/index.php?showtopic=17474&hl=development+tools)
-
I've been struggling recently with a few things, such as library locations. If I choose to install something to /mnt/user using the package manager, the library will not be found after a reboot.
Changing /etc/ld.so.conf to add the path /mnt/user/usr/lib/ and then running ldconfig sorts this out.
Should this path be added to the baseline pdaxrom config?
I don't think this problem is due to the library path per se. It's more likely that it's the generic problem of missing symlinks. In case you didn't know, when you install packages onto external storage (ie anything other than "/"), symlinks are created within the "/" which points to those files in external storage. Now for some reason (which I haven't figured out yet) when you reboot sometimes the symlinks go AWOL and hence your problem. And the wierd thing is that not all symlinks are affected. What I did to get around this was to force all symlinks to be recreated on bootup. Sure, this increases the startup time but it's not often that I have to reboot so it's a minor issue.
-- cheers
-
Thanks DesertRat, that would explain it! You're absolutely right: the system worked until I rebooted, and the reboot seems to have killed the symlinks.
Sorry for the simple question, but how did you force symlinks to be recreated on boot?
-
In case you didn't know, when you boot up, a background process begins restoring symlinks. If you have loaded up your Z with lots of packages (lots of files), the process can take quite a while, during which time certain things wont work. My strategy is to install most lib packages in /, that way they are always present. In addition, any network type applications also go in / as opposed to on a CF card, since sometimes you may want GPS or WIFI in the CF slot.
Also, if you are not compiling stuff, don't put gcc headers and the other tools on your Z. That's a lot of files.
-
Sorry for the simple question, but how did you force symlinks to be recreated on boot?
I placed this in my /etc/rc.d/init.d/pcmcia script:
ipkg-link mount /mnt/hdRun ipkg-link without any parameters to see some help.
-- cheers
-
Hmm... I though all symlinks are automatically recreated on each boot (which is annoying for me, I have everything installed on /dev/hda3 and it takes about 10 minutes after a reboot for everything to work properly).
Thank god I don't reboot that often. :-)
Speaking of which, is there a way to disable ipkg-link's behaviour with linking-unlinking packages on reboot? I'm talking about packages on /dev/hda3 which is always present...
-
Thanks again. No, I didn't know that
I do have gcc headers installed... I guess that's why it takes a while to recreate 'em.
-
In case you didn't know, when you boot up, a background process begins restoring symlinks.
OK I found the two places where ipkg-link is called, one is where pcmcia is started and the other is for the SD card. Since all my apps are installed on the microdrive only the pcmcia part is relevant to me.
AFAICS ipkg-link is called from within a function that is related to the automounting of partitions controlled by /etc/pcmcia/ide.opts. But as I note in this thread ...
https://www.oesf.org/forums/index.php?showtopic=16560 (https://www.oesf.org/forums/index.php?showtopic=16560)
... I can't get my ext3 partition to "automount", and hence ipkg-link will not run.
-- cheers
-
In case you didn't know, when you boot up, a background process begins restoring symlinks.
OK I found the two places where ipkg-link is called, one is where pcmcia is started and the other is for the SD card. Since all my apps are installed on the microdrive only the pcmcia part is relevant to me.
AFAICS ipkg-link is called from within a function that is related to the automounting of partitions controlled by /etc/pcmcia/ide.opts. But as I note in this thread ...
https://www.oesf.org/forums/index.php?showtopic=16560 (https://www.oesf.org/forums/index.php?showtopic=16560)
... I can't get my ext3 partition to "automount", and hence ipkg-link will not run.
-- cheers
[div align=\"right\"][a href=\"index.php?act=findpost&pid=114940\"][{POST_SNAPBACK}][/a][/div]
Perhaps just call it again in your own script that mounts the CF drive... can't hurt.