GASH schema changes proposed for dev3

[Jonathan Abbey <jonabbey@arlut.utexas.edu>]

Oops, let me clarify:

| In terms of GASH compatibility, however, it doesn't work very well.  We have
| implemented some code to generate the GASH hosts_info file out of Ganymede
| running the GASH schema.  With this code, it will be possible to use Ganymede
| as essentially a drop-in replacement for GASH.

That is to say, we have developed the hosts_info emitting code with the
current GASH schema, but it will throw out any data in the database that
cannot be expressed in the hosts_info file.  This means that your users
might proceed to enter system data into Ganymede that will then be lost
when the hosts_info file is generated.  This is undesirable, so we are
thinking of simplifying the GASH schema to prevent this from occurring.

In the process of simplifying the GASH schema, we would also re-introduce
the relatively simple system GASH uses for assigning I.P. addresses (a
selection of class C-sized networks attached to individual rooms) to make
the GASH schema fully functional at the level of GASH.

Again, let me know if you have any feedback (or questions).

-------------------------------------------------------------------------------
Jonathan Abbey				              jonabbey@arlut.utexas.edu
Applied Research Laboratories                 The University of Texas at Austin
-------------------------------------------------------------------------------

----------------------------------------------------------------------------
To make changes to your subscription to the ganymede mailing list, send
mail to majordomo@arlut.utexas.edu.

To unsubcribe, include the line

unsubscribe ganymede

in the body of your mail message

To see the latest design specs for Ganymede, visit the Ganymede web page
at http://www.arlut.utexas.edu/gash2/
----------------------------------------------------------------------------