John,
Hello again! I can help a little with 1 and 3.
On Tuesday, September 30, 2003, at 05:36 pm, John Murdie wrote:
- I wish to install Poly/ML 4.1.3 on Linux. Since we don't usually
install from RPMs, I first downloaded and unpacked the tar file of the binary release. With the files in a single directory, ./polyml worked fine: ... $ ./poly Poly/ML RTS version I386-4.1.3 (13:57:33 Sep 30 2002) Copyright (c) 2002 CUTS and contributors. Running with heap parameters (h=10240K,ib=2048K,ip=100%,mb=6144K,mp=20%) WARNING:/usr/local/lib/poly/ML_dbase: Write permission denied. WARNING:/usr/local/lib/poly/ML_dbase: Opened for reading only. Mapping /usr/local/lib/poly/ML_dbase Poly/ML 4.1.3 Release
Does this matter?
No. In fact, so far, it hasn't reported an error, but it will when it reads end-of-file.
If so, if the database must be generally writeable, I think that this is rather unfortunate.
The master database does not need to be writable. It looks like an error when you run poly on a read-only database and terminate the session with an end-of-file, but it isn't. You will find when you use Poly/ML to build ProofPower that our mods to the read-eval-print loop bypass the automatic attempt to save the state in the database that is causing the apparent error.
- There are no Unix manual pages for Poly/ML, either for the command
or for the library routines. I'd write some, but I think the developers will know best what to write. The Linux manual page man(7) explains the format best, I've found.
As a workaround, poly -? will tell you about most of the options (I think some recent options to do with minimum and maximum database sizes aren't in there yet).
Over to David for the real facts ...
Regards,
Rob.