3.3.6pre1 smbfs on 3.5.1

[MrSquishy]

I've got the old version of smbclient working by using the smbclient, libsmbclient and smbfs packages from 3.3.6pre1 and installing them manually out of the data.tar.gz's.
But since they are not installed through ipkg, ipkg-link mount /mnt/card doesnt pick it up. Meaning I have to symlink it by hand after a reboot.  Is there anyway to fake-out ipkg into thinking these were installed like a normal ipk so that ipkg-link will work on it?


(I'll gladly post what I did to get smbmount working if someone wants to know.)

[lardman]

A couple of questions:

1. Why don't you use the samba packages from 3.5.1 (the samba package certainly has smbclient in it, I've not looked at smbfs).

2. Why don't you just install the packages normally using ipkg? If they are complaining about dependencies then use -force-depends.

The way you're doing it seems very painful.


Si

[zenyatta]

Dumb question of the day: can you guys explain to me (or point me to an explanation of) why symlinks break upon reboot? Thanks.

In my case, ipkg-link works but not automatically. I have to run it by hand (it may be due to the fact that my CF card is multi-partitioned - some hard-coded boot script probably tries to mount /mnt/cf instead of the actual mount point). It's a pain for sure.

z.

[MrSquishy]

Oh, it is painful, but I want to be able to do smbmount.  And 3.5.1 Samba doesnt seem to want to.

I cant do ipkg install because it screams about expecting archtype= something something...  In fact, it seems a lot of 3.3.6pre1 packages do that. (this and qtopiagnuboy at least)


I think the problem with ipkg-link is that it doesnt obey ipkg.conf's dests.  It is setup to only look at /mnt/ram, /mnt/cf and /mntcard.  Am I wrong?

[lardman]

I think the problem with ipkg-link is that it doesnt obey ipkg.conf's dests. It is setup to only look at /mnt/ram, /mnt/cf and /mntcard. Am I wrong?

Look here: https://www.oesf.org/forums/inde...?showtopic=6420

I cant do ipkg install because it screams about expecting archtype= something something... In fact, it seems a lot of 3.3.6pre1 packages do that. (this and qtopiagnuboy at least)

kergoth explained this to me a while back on irc; he said it was to do with the arch line (in the control file in control.tar.gz in the ipk I assumed) not appearing in the ipkg configuration file (/etc/ipkg.conf). This is probably not a very good explanation of what he said; my fault.

I don't know what the arch lines in /etc/ipkg.conf actual mean/do; for example mine say this (and it changes on a per machine basis, mine's a Shepherd):

Code: [Select]

arch all 1
arch any 1
arch noarch 1
arch arm 10
arch shepherd 20
Anyone care to shed any light (though this is going off topic now)?


Si

P.S. If you really want to use these files without using ipkg, take a look in /usr/lib/ipkg/info/ and look at the files in there. One (for each package) is a list of the package's files, I reckon if you create one of these and place it there (as well as the other bits, and adding the package details to /usr/lib/ipkg/status, you might get ipkg-link to work)

[adf]

This would be essentially along the same lines as "porting" pdaXrom srtuff, it  appears. Will any of the xrom stuff work on a 5500 (if correctly dissected and transplanted)?

[lardman]

This would be essentially along the same lines as "porting" pdaXrom srtuff, it appears.

If by port you mean converting from X11 to using the framebuffer, then no not at all.

If you mean fixing the 'broken' control files in pdaXrom ipks then yes, similar (but I'm not sure if this is the (only?) fix which must be applied to the pdaXrom ipks).

Will any of the xrom stuff work on a 5500 (if correctly dissected and transplanted)?

A qualified no: PdaXrom apps are compiled to arm5 code, the 5500 can only run arm4. You may be lucky and find an app which doesn't have any of the new arm5 instructions. Probably (almost certainly) not though.

On a 5600/Cxxx they would work (assuming you fix the control files and grab the dependencies and probably use GPE, unless you're after a command line app)


Si

[Hrw]

OZ 3.5.1 images have /etc/ipkg/arch.conf file with all arch info. It is read by opie-packagemanager (via libipkg) and by ipkg itself.

opie-aqpkg doesn't use it so if you use it then have to add contents of that file into /etc/ipkg.conf - maybe it will help.

[zenyatta]

To answer my own question: symlinks break after reboot when opie-symlinker is not installed. I must have uninstalled it by mistake.

z.