Return-Path: Received: from punt-1.mail.demon.net by mailstore for rleyton@dogbert.demon.co.uk id 886024367:09:03699:0; Wed, 28 Jan 98 21:52:47 GMT Received: from mail.acm.org ([199.222.69.4]) by punt-1.mail.demon.net id aa1410774; 28 Jan 98 21:51 GMT Received: from brookes.ac.uk (csmail.brookes.ac.uk [161.73.1.1]) by mail.acm.org (8.8.5/8.7.5) with ESMTP id QAA42036 for ; Wed, 28 Jan 1998 16:50:47 -0500 From: majordomo@brookes.ac.uk Received: by brookes.ac.uk (8.8.7/) id VAA05799; Wed, 28 Jan 1998 21:51:02 GMT Date: Wed, 28 Jan 1998 21:51:02 GMT Message-ID: <199801282151.VAA05799@brookes.ac.uk> To: rleyton@acm.org Subject: Majordomo file: list 'leap' file 'leap.9801' Reply-To: majordomo@brookes.ac.uk X-Mozilla-Status: 8001 -- >From leap-owner Sun Jan 25 17:53:42 1998 Received: by brookes.ac.uk (8.8.7/) id RAA09254; Sun, 25 Jan 1998 17:52:58 GMT Message-ID: <34CB75C9.81422151@acm.org> Date: Sun, 25 Jan 1998 17:26:33 +0000 From: Richard Leyton X-Mailer: Mozilla 4.04 [en] (Win95; I) MIME-Version: 1.0 To: LEAP Mailing List Subject: leap list: System installation Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: leap@brookes.ac.uk Precedence: bulk Reply-To: leap@brookes.ac.uk Ladies and Gents, I've been asked to give a presentation on LEAP at my old University (Oxford Brookes). One of the things I will be doing is explaining to the students how they can install LEAP for themselves at college, and at home. I'm well aware that LEAP does have a large footprint if students all compile and install their own copies. Therefore, my plan at the moment is to write a script to setup a LEAP directory with symbolic link to shared directories (such as src, config and so forth), and to copy a baseline installation of the database directory, to allow them to work on their own copy. If you've already done something similair, I'd much appreciate it if you could drop me (or the list) a copy of the process/script you used. This is something I'd like to include in the next release of LEAP. Comments are also welcome. On the subject of next releases, it'll appear when it appears. I'd like to think it'll pick up momentum over the next few weeks, but cannot promise anything, work being what it is. I will be making my presentation notes available on the Web a day or two after the presentation (Thursday, 5th February). Regards, Richard. PS. FYI I will be basing the presentation on LEAP 1.0 - and demonstrating it (if all goes according to plan) on Solaris 5.5.1 -- Richard Leyton mailto:rleyton@acm.org >From leap-owner Mon Jan 26 21:35:38 1998 Received: by brookes.ac.uk (8.8.7/) id VAA29109; Mon, 26 Jan 1998 21:34:43 GMT Message-ID: <34CCFFA3.AE97506A@acm.org> Date: Mon, 26 Jan 1998 21:26:59 +0000 From: Richard Leyton X-Mailer: Mozilla 4.04 [en] (Win95; I) MIME-Version: 1.0 To: LEAP Mailing List Subject: leap list: Release of LEAP 1.1.8 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: leap@brookes.ac.uk Precedence: bulk Reply-To: leap@brookes.ac.uk LEAP 1.1.8 has just been uploaded to the various ftp sites: * via ftp server in Britain: ftp://ftp.demon.co.uk/pub/compsci/databases/leap/leap-1.1.8.tar.gz * via web server in California: http://sunsite.unc.edu/pub/Linux/Incoming/leap-1.1.8.tar.gz * via ftp server in California: ftp://sunsite.unc.edu/pub/Linux/Incoming/leap-1.1.8.tar.gz * Ultimate location in California: ftp://sunsite.unc.edu/pub/Linux/apps/database/relational/leap-1.1.8.tar.gz * Search FTP Sites - Search for leap-1.1.8.tar.gz - The sunsite site is very heavily mirrored around the world. The web site has been updated to reflect these new links. It's URL is, of course http://www.dogbert.demon.co.uk/leap.html Please note that the Sunsite ftp server's Linux section is not currently being actively maintained, so the LEAP distribution is likely to remain in /pub/Linux/Incoming for some time. However, this is mirrored around the world very quickly, so serves it's purpose. The demon site is excellently maintained, and the file should appear within 48 hours. 1.1.8 fixes a lot of the bugs that made the 1.1.7 release such a fiasco. It was properly uploaded for a start! I've tested it as thoroughly as I can, and cannot find any serious problems. Here's a full list of 1.1 features as they stand at the moment: * Self contained relations, no separate files (.tmp, .fld, .rel) * Separate Utilities included for conversion/analysing databases. * Command line editing using GNU readline, gives Emacs, vi like editor * delete routine implemented. * Activity log implemented to record user activity. * Database to open specified on command line (-b dbname). * Optimisation step * Incorrectly specified "create relation" commands clean up if incorrect data type specified. * create database operator * reverse operator implemented - To reverse engineer a database. * create relation can be nested. * LEAP completely auto installs (No database hierarchy in source distribution any more. A single .src script does it all) * LEAP can be installed with a small footprint for multiple users on a single system. Only files that change are stored in the users home directory. The biggest change, apart from the bug fixes, is the inclusion of the small footprint installation. After my e-mail over the weekend, I sat down and hacked out a simple solution which does the trick. On a Linux box a small installation requires about 200k - much better than the full 1.5M+ required for a full LEAP installation, library and set of object files. I'd still appreciate any other solutions you might use - mine is really very basic. 1.1.8 is therefore the version you should download if you fancy experimenting with the new LEAP features.. If all goes well (Note the more cautious tone here...) this will be the last release with any new functionality. I'm hunting memory leaks now. I'll also try and make a concerted attack on getting the documentation up to date. I look forward to hearing from you soon... Regards, Richard. -- Richard Leyton mailto:rleyton@acm.org >From leap-owner Mon Jan 26 22:00:17 1998 Received: by brookes.ac.uk (8.8.7/) id WAA00900; Mon, 26 Jan 1998 22:00:11 GMT Message-ID: <34CD0093.1BBE93AF@acm.org> Date: Mon, 26 Jan 1998 21:31:00 +0000 From: Richard Leyton X-Mailer: Mozilla 4.04 [en] (Win95; I) MIME-Version: 1.0 To: LEAP Mailing List Subject: leap list: Base installation for large numbers of users Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: leap@brookes.ac.uk Precedence: bulk Reply-To: leap@brookes.ac.uk If you get a chance, please take a look at the new script included in LEAP 1.1.8 which allows a single installation of LEAP to be made in some central location on a machine. I've attached the documentation I threw together to give you an idea of what it's all about, and how to go about it (it's scripts/users/README in the 1.1.8 distribution). I'd appreciate any comments you might have. Regards, Richard. > These scripts are included to make LEAP easier to use in a large user environment. > > SETTING UP THE BASE INSTALLATION > ================================ > In order to make the installation process as simple as possible, first > make sure you can compile and run LEAP in your environment. You may modify > the help pages, or included databases as much as you like. Set the > configurations as you feel appropriate. > > Once you are satisfied with your installation, copy it to a location that ALL > users can access. On a Solaris installation, for example, this might be > /opt/LEAP. Request that the Systems Administrator (SA) gives you alone > write permission. Students/Users should NOT have write permission to > this directory (755). > > Now COPY all of the LEAP installation across to this directory, with: > > cp -r LEAP_source_directory LEAP_target_directory > > Check the directory contains something like the following with "ls -l": > > -r--r--r-- 1 rleyton users 4565 Dec 8 23:30 BETA > -r--r--r-- 1 rleyton users 17982 Nov 22 1996 COPYING > -r--r--r-- 1 rleyton users 7721 Nov 22 1996 INSTALL > -rw-r--r-- 1 rleyton users 3192 Jan 25 23:41 NEWS > -rw-r--r-- 1 rleyton users 2961 Dec 17 21:02 NOTES > drwxr-xr-x 2 rleyton users 1024 Dec 17 21:03 RCS > -r--r--r-- 1 rleyton users 2755 Dec 14 18:44 README > -r--r--r-- 1 rleyton users 783 Dec 14 18:53 TODO > drwxr-xr-x 2 rleyton users 1024 Nov 24 1996 bin > drwxr-xr-x 3 rleyton users 1024 Oct 15 20:35 configs > drwxr-xr-x 7 rleyton users 1024 Jan 25 22:50 database > drwxr-xr-x 3 rleyton users 1024 Jan 25 23:30 doc > drwxr-xr-x 3 rleyton users 1024 Oct 15 20:38 help > -r--r--r-- 1 rleyton users 760 Dec 14 18:44 leap-1.1.lsm > drwxr-xr-x 6 rleyton users 1024 Jan 25 23:38 ltest > drwxr-xr-x 2 rleyton users 1024 Dec 13 21:15 report > drwxr-xr-x 4 rleyton users 1024 Jan 25 23:03 scripts > drwxr-xr-x 7 rleyton users 2048 Jan 25 22:57 src > > Now run LEAP_source_directory/scripts/users/buildtar > > You will be prompted to enter the base directory (eg. /opt/leap). You will also > be prompted to enter the target directory for LEAP's central build. By default > this is the directory you just specified with /build appended. > > Completing this will create a tar file that contains a copy of changeable > files (database, configs, and reports). Symbolic links are set up for all > other directories. > > The tar file is stored in the target directory. Check it with > "tar tvf leap_build.tar" to list the contents. > > If some users are likely to want to take LEAP to their own Unix machines > (such as Linux box at home), several options present themselves: > > - Create a tar file of the build directory which can be transferred at > will. > - Place the file on a central NFS server from which the LEAP install > directory can be mounted by all clients (obviously not practical for > home access!). > - Suggest users compile LEAP for themselves (See below). > > Remember to make sure users are aware of machine compatibility issues. > > If you feel that some users may wish to compile LEAP for themselves, a > suggestion would be to place the original LEAP distribution file in > the target directory. This will save repeated downloads from ftp servers. > Instructions for advanced users are included at the end of this file on > the assumption this is where the file has been placed. > > > INSTRUCTIONS FOR USERS > ====================== > The following instructions can be passed out to users of LEAP in order to get a > copy of LEAP installed with minimal problems. Change the $LEAPINSTALLDIR to > the directory in which LEAP was installed (!). > > In order to install LEAP, run the script: > > $LEAPINSTALLDIR/scripts/users/leapinstall > > You will be asked to enter the LEAP source directory. This is $LEAPINSTALLDIR. > > A target directory is then required. This should be in your home ($HOME) > directory. It defaults to the directory in which the script is being run. > Specify $HOME/leap in order that the LEAP installation is in its own > directory. > > LEAP will then proceed to extract all necessary files from the archive, and > create links to files that can be shared. > > eg. Sample installation script (with installation dir /opt/leap): > -------------------------------------------------------------------------------- > bash$ /opt/leap/scripts/users/leapinstall > Enter the LEAP installation source directory: > /opt/leap/build > Enter leap target directory [/home/rleyton/leap] > /home/rleyton/leap > Completed. > bash$ cd /home/rleyton/leap > bash$ ls -l > total 4 > lrwxrwxrwx 1 rleyton users 41 Jan 25 23:57 BASEINSTALL.README -> /opt/leap/doc/baseinstall.README > lrwxrwxrwx 1 rleyton users 26 Jan 25 23:57 COPYING -> /opt/leap/COPYING > lrwxrwxrwx 1 rleyton users 23 Jan 25 23:57 NEWS -> /opt/leap/NEWS > lrwxrwxrwx 1 rleyton users 24 Jan 25 23:57 NOTES -> /opt/leap/NOTES > lrwxrwxrwx 1 rleyton users 25 Jan 25 23:57 README -> /opt/leap/README > lrwxrwxrwx 1 rleyton users 23 Jan 25 23:57 TODO -> /opt/leap/TODO > drwxr-xr-x 2 rleyton users 1024 Jan 25 23:48 bin > drwxr-xr-x 3 rleyton users 1024 Oct 15 20:35 configs > drwxr-xr-x 7 rleyton users 1024 Jan 25 22:50 database > lrwxrwxrwx 1 rleyton users 22 Jan 25 23:57 doc -> /opt/leap/doc > lrwxrwxrwx 1 rleyton users 23 Jan 25 23:57 help -> /opt/leap/help > lrwxrwxrwx 1 rleyton users 31 Jan 25 23:57 leap-1.1.lsm -> /opt/leap/leap-1.1.lsm > drwxr-xr-x 2 rleyton users 1024 Dec 13 21:15 report > lrwxrwxrwx 1 rleyton users 22 Jan 25 23:57 src -> /opt/leap/src > -------------------------------------------------------------------------------- > > In order to run LEAP, change directories to the LEAP target directory you > specified at the second prompt (eg. /home/rleyton/leap), and type: > > bin/leap > > eg. Starting LEAP for the first time > -------------------------------------------------------------------------------- > bash$ bin/leap > LEAP 1.1.8 - An extensible and free RDBMS > Copyright (C) 1997, 1998 Richard Leyton. > > LEAP comes with ABSOLUTELY NO WARRANTY; for details type "warranty". > This is free software, and you are welcome to redistribute it > under certain conditions; type "copying" for details. > ***************************** > * THIS IS A >>BETA<< REVISION > ***************************** > LEAP is starting... > No hash table exists for relation zzrrag - Creating... Done. > No hash table exists for relation zzmrbw - Creating... Done. > Startup sequence initiated. > :-) > -------------------------------------------------------------------------------- > > For further information on LEAP usage, see the manual in doc, or consult > your lecture handouts. > > More information on LEAP is available on the LEAP web site: > > http://www.dogbert.demon.co.uk/leap.html > > For announcements, and information, join the LEAP mailing list by sending a one > line e-mail to: majordomo@brookes.ac.uk containing "subscribe leap" in the > body of the message. > > ADVANCED USERS > ============== > Advanced users may want to compile and run LEAP for themselves, with any > changes they wish to make. The easiest solution is to check to see if the > original distribution is presen in the LEAP Installation directory > (eg. /opt/leap/build) - Copy the file to your directory, uncompress and > extract the file, and read the file INSTALL. > > If the file is not present, consult your lecturer, especially if you do > no have access to the Internet, or if you do not have a particularly > fast link. > -- Richard Leyton mailto:rleyton@acm.org >From leap-owner Tue Jan 27 12:51:13 1998 Received: by brookes.ac.uk (8.8.7/) id MAA18041; Tue, 27 Jan 1998 12:50:32 GMT Message-Id: Date: Tue, 27 Jan 1998 13:51:29 +0100 (MET) From: Klaus Schilling To: leap@brookes.ac.uk Subject: leap list: wrapping leap into scripting langs Sender: leap@brookes.ac.uk Precedence: bulk Reply-To: leap@brookes.ac.uk Would it be feasible to interface Leap to scripting languages such as Perl, Python, Tcl, guile etc. ? As applications, leap might be invoked then easily from CGI scripts, or bots (expect-based), or be integrated into GUIs via Tk. I guess I'm too euphoric now, but it could be worth a trial. Klaus Schilling >From leap-owner Tue Jan 27 14:21:22 1998 Received: by brookes.ac.uk (8.8.7/) id OAA06052; Tue, 27 Jan 1998 14:21:10 GMT Message-ID: From: "Leyton, Richard" To: "'leap@brookes.ac.uk'" Subject: RE: leap list: wrapping leap into scripting langs Date: Tue, 27 Jan 1998 14:15:25 -0000 X-Priority: 3 X-Mailer: Internet Mail Service (5.0.1458.49) Sender: leap@brookes.ac.uk Precedence: bulk Reply-To: leap@brookes.ac.uk Klaus, Thanks for the e-mail. The LEAP API is my start at opening LEAP up to enable it to be incorporated into other environments as easily as possible. Once a database handle is opened, it should be relatively easy for normal relational/tuple operations to be executed (even, perhaps ultimately, if it's a totally different machine over a network). In a sense, this is what goes on in the database.c module - which maintains the data dictionary and operations on it (although it doesn't yet use the API). Take a look at 'apitest.c' for an example of playing around with the API in LEAP 1.1.8 (just released). I've been playing with the _idea_ of a tk based GUI to LEAP, but think it is more likely a GUI of some description would be better set up using a web based solution. It would be more 'portable' that way to other platforms. However, that would require a CGI script of some description at the back end, which, of course, would require some mechanism by which LEAP can be interfaced to. Perl I think is probably the best bet, because it allows C libraries routines to be called. I am however at a loss on how to start developing this. Work clearly won't allow it, and home Linux setup would probably do for starters, but not much use when trying to roll it out in any shape or form... Hopefully I might be able to sort something out with Brookes University in the near future... I'd (eventually) like to have a web page which allowed remote users to experiment with a LEAP installation of some description... Try-before-you-buy sort of thing... Unfortunately, time is always in short supply. If anybody is interested in perhaps exploring some of these avenues in more detail... LEAP is distributed under the GPL for this very reason. Regards, Richard. -- Richard Leyton, Data Services Systems Administrator Global Technology - Europe, Salomon Smith Barney Tel: +44 (0)171 721 6503 Fax: +44 (0)171 721 2605 mailto:richard.leyton@ssmb.com > ---------- > From: Klaus Schilling[SMTP:klaus@debian.sbi.com] > Sent: January 27 1998 12:51 > To: leap@brookes.ac.uk > Subject: leap list: wrapping leap into scripting langs > > > Would it be feasible to interface Leap to scripting languages such as > Perl, > Python, Tcl, guile etc. ? > > As applications, leap might be invoked then easily from CGI scripts, > or bots > (expect-based), or be integrated into GUIs via Tk. > > I guess I'm too euphoric now, but it could be worth a trial. > > > Klaus Schilling >