Posted: Tue 22 Jan 2013, 10:28 Post_subject:
Modifying with sfs files. Soft link problem. [SOLVED] Sub_title: I thought a folder/file/link in the sfs should have precedence?
It's the case of RTFM another time to get it right fatdog64 who I linked to belove has modified the squashfs layout compared to the original. So I figure my best bet is to have my seamonkey link in /bin rather than /usr/bin
I have made a browser sfs to keep my seamonkey up-to-date
The only problem is that my modified seamonkey link in the sfs is not the one chosen by puppy.
This is what it looks like:
# which seamonkey
# ls -l /initrd/pup_ro4/usr/bin/seamonkey
lrwxrwxrwx 1 root root 24 Jan 22 2013 /initrd/pup_ro4/usr/bin/seamonkey -> /opt/seamonkey/seamonkey
# ls -l /usr/bin/seamonkey
lrwxrwxrwx 1 root root 35 Oct 18 06:23 /usr/bin/seamonkey -> /usr/lib/seamonkey-2.13.1/seamonkey
The listing is taken from a puppy (precise) running in ram. No save file. No configuration done except for loading my sfs file.
I thought the /initrd/pup_ro4/usr/bin/seamonkey would have precedence over the original /usr/bin/seamonkey link? (as this explanantion indicates).
Wonder if someone could point me in the right direction?