View source for Paroli-developer-setup
From Openmoko
You do not have permission to edit this page, for the following reasons:
You can view and copy the source of this page:
Return to Paroli-developer-setup.
You do not have permission to edit this page, for the following reasons:
You can view and copy the source of this page:
Return to Paroli-developer-setup.
To be able to test the latest paroli directly on the phone, the simplest method to mount the local paroli source via nfs. Maybe sshfs works too. Need somebody to document sshfs way.
sudo apt-get install nfs-kernel-server
The /etc/exports file:
/home/[username]/[path to paroli] 192.168.0.202(rw,sync,no_subtree_check,anonuid=0,anongid=0)
Restart the nfs server:
/etc/init.d/nfs-kernel-server restart
sudo ip address add 192.168.0.200/24 dev usb0
ssh root@192.168.0.202
mount -t nfs 192.168.0.200:/home/[username]/[path to paroli] /usr/share/nfs-paroli
cd /usr/share/nfs-paroli/paroli-applications; ./build.sh
cd /usr/share/nfs-paroli/paroli-scripts; ./paroli-launcher.sh
NOT READY YET
Enlightenment 17 (E17) used by Paroli is a big bunch of code which is not readily packaged to most distributions (largely because no release is declared stable so it's a moving target). One script to help installing E17 is available at omicron, Easy_e17.sh.
Easy_e17 checks out and installs most of E17 automatically, under /opt/e17. If you dislike running random scripts from the web, check the script first before running. You can rerun it with "-u" to update or "-i" to try installing again if for example some dependencies were missing during the first run. If some compilation fails, check out the error message and install needed dependencies. It may get a few iterations of "-i" before you get to the finish without errors, so prepare to spend some time.
Easy_e17 does not seem to install Python bindings E17, but it does download them. By default you can find them in your home directory under ~/e17_src/BINDINGS/python. Those are required for Paroli.
(to be continued)
Check out Paroli source code from the git repository as usual. Set up your environment to use the E17 installed with something like follows:
export PATH=${PATH}:/opt/e17/bin export LD_LIBRARY_PATH=${LD_LIBRARY_PATH}:/opt/e17/lib export PKG_CONFIG_PATH=${PKG_CONFIG_PATH}:/opt/e17/lib/pkgconfig
Run build.sh under paroli-applications and then paroli under paroli-scripts. If you get a complaint about "No module named elementary", you are (still) missing the E17 Python bindings.
Sadly NO. There were a map_static option, but it was removed in nfs-kernel-server. Here is a 5 year old bugreport about this issue: https://bugzilla.redhat.com/show_bug.cgi?id=130261
Certainly. It permits to anybody (on your local network) to be able create files with the remote uid. Root(uid=0) in our freerunner case.
Yepp, this is the alternative to using anongid/anonuid in /etc/exports.
Yepp, sshfs would be the easiest. Need somebody to figure out the steps, and update this doc.