Philips Independent User Group web page. The information and opinions on this site neither belong to or are endorsed by Philips. Individuals have submitted these pages, they may be used at the surfer's own risk. Any programs copied down should be tested thoroughly by the end user. No liability rests with the author, Philips or the hosts of the site.
Making a remote Odyssey file system and transferring patients to it.
The remote system:
You'll need a remote file system to push them to. Most simply it is a Linux computer with some partitions off the root called /img7 /img8 img9 (that is /img followed by any number you aren't already using on your Odyssey(s)). These partitions have to be made accessible to the Odyssey by placing each Odyssey name in the /etc/hosts.equiv file. The "name" of the Odyssey is just any convenient name you wish to use and applies only within the linux computer. It is identified with an IP address in the /etc/hosts file. e.g. a line might read: 184.108.40.206 Odyssey1. You also need to export the file systems so that nfs can use them. Start webmin by opening a browser on the linux box by entering its own IP address as the URL, followed by :10000 (e.g. th IP address is 220.127.116.11 so in the browser address bar type 18.104.22.168:10000). Accept cookies, login with user admin and password same as root on the linux box. In case you don't have webmin, exporting the file system seems to add a line to /etc/exports, which is:
/img7 22.214.171.124 (rw,no_root_squash,insecure)
where the IP address above is the address of the odyssey. Finally the linux and the Odyssey are obviously going to have to be connected to a network. If you insist on using a microsoft computer, there is a program which makes a dos partition look like a unix partition, but you'll have to ask about for it, I can't remember its name.
On the Oddysey:
Again we need to name the linux machine in the /etc/hosts file. Lets call it "linuxbox". The main macro to do the biz is called transfer.pmf. This pixie macro calls 2 very small and not at all frightening shell scripts called is_it_mounted and get_asn. Functionality is that the operator is asked for the name of the partition to transfer to, (it must already be mounted). The macro then examines it to check it is really a remote file system (is_it_mounted does this) and if it is, it checks to see if there is an index already on it. If there is not it makes one, if there is it runs through the directories to find the highest ASN (Pnumber). It then increments it, makes a directory and starts transferring the first patient on the workbench. When it comes to the next patient on the workbench it increments the ASN again makes a directory and transfers that patient, until its done them all.
Limitations: There is no explicit verification that the file on local disk is the same as the file on the remote disk, the macro relies on the shell cp command to trap any transfer errors, which I think it does quite reliably. There is also no check that the remote partition has enough space to receive all the patients. But the re is another macro (wb_size.pmf) which reports on the total kB of patients on the workbench. If you run wb_size.pmf you must close Pixie and reopen it before running transfer.pmf. Also note about wb_size.pmf: it measures the size of all patient studies for whom any file is found on the workbench, e.g. even if you only put one lightbox on the workbench, wb_size.pmf will return the size of the whole patient directory the lightbox came from.