| Agitprop | The Cabal | DRT | Games | Library | Lookie Here | Software | Projects | ||||
| |||||||||||
|
This is the stuff we need to establish standard desktop connectivity as well as certain basic tools. We assume the Z can talk to the net. Again, execute the commands through an SSH connection or Opie Termnal. Opie-SHWe like Opie-SH, and use it for a number of things. You can learn more about it at the Opie-SH homepage. Also, a copy of the Opie-SH howto is intalled with the program.
In addition to Opie-SH itself, we have installed a couple of Opie scripts. One of these, launcher_refresh.sh, refreshes Opie's GUI after we've installed applications from the command line. If any icons are installed, they won't appear until this happens. Try it now, since we've just installed some icons. Look, they aren't there. now, execute "launcher_refresh.sh" and wait for a second or two. A confirmation screen will show on the Z's display, and the new icons will now be visible. NFSWe are using NFS to mount the Z's filesystem on our desktop (and vice versa). This requires configuration on both the Z and the desktop machine. Alternatively, if you have a larger SD card, you can install the Samba package and use that. Samba is huge, though, so we've left it off. We like NFS better anyway. On our desktop, NFS was installed with the distribution, so all we had to do was configure it. To do so, we added the following lines to /etc/hosts.allow portmap: 192.168.129.201 lockd: 192.168.129.201 rquotad: 192.168.129.201 mountd: 192.168.129.201 statd: 192.168.129.201 We also added the following lines to /etc/hosts.deny portmap: ALL lockd: ALL mountd: ALL rquotad: ALL statd: ALL And, lastly, added this line to exports: / 192.168.129.201(rw,sync) This is a maximally restrictive setup -- NFS mounts will only be allowed between the desktop and the Z when the Z is in the cradle. If you want to allow mounts to occur over your LAN, then you'll need to expand the scope a bit. For example, instead of using 192.168.129.201, you could use 192.168.0.0/16. For convenience, we also put this line in the desktop's /etc/fstab: 192.168.129.201:/ /mnt/nfs nfs noauto,user 0 0 and create the /mnt/nfs directory if it doesn't exist. Then we can issue a simple "mount /mnt/nfs" (or use KDE's mounting icons) to access the Z. Issue the command "/etc/init.d/nfs restart" to make your desktop use the new configuration. On the Zaurus side of things:
You can now use NFS to access the filesystem on the other computer. On the Zaurus, trying issuing the command "mount /mnt/desk", and the desktop's filesystem will appear in /mnt/desk. You'll be accessing it with root permissions, so beware. "umount /mnt/nfs" to unmount, of course. On the desktop, try "mount /mnt/nfs", with the same results. Because you access the mounted filesystem using the permission of the user you're logged in as, you might find it convenient to create non-root users on the Z (use adduser) to match your non-root users on the desktop, so they have an area on the Z they can write to. OpenSSHDropbear sucks. Put OpenSSH in instead. There's a couple of ramifications to this. First, if you've been using ssh up to now, then when we change to OpenSSH the Z's fingerprint will change. The next time you try to ssh to the Z, your program should complain about that (if it doesn't, get an ssh client that works properly). Also, we're only replacing DropBear on this boot card. If you boot the Z without the card inserted, it will be using DropBear again -- which means the Z's fingerprint will change again.
Your new openssh won't be running until you reboot the Z. Miscellaneous
|
Sections:
See Also: Opie-SH A collection of Opie-SH scripts NFS Howto Open SSH |
| ODD# ivii(w)/BBC,-1272369549;33Dsc3176 | (K)3176 by The Barry Bittwister Cabal. All Rites Reversed. |