Broken system web pages - ideas?

[L. D. Marks]

While testing a package on a number of systems, it
has become clear to me that they are often "broken"
in non-obvious ways. As just two examples that I
have come across:
        1) Users not having permissions to shared libraries
        2) Duplicate, and inconsistent gcc/g++/g77 compilers

Has anyone ever collected a list of these, and suggestions
of what to do on a web page? (I would be glad to collate
these if you want to send them to me off-line.)

-----------------------------------------------
Laurence Marks
Department of Materials Science and Engineering
MSE Rm 2036 Cook Hall
2225 N Campus Drive
Northwestern University
Evanston, IL 60201, USA
Tel: (847) 491-3996 Fax: (847) 491-7820
mailto:address@hidden
http://www.numis.nwu.edu
-----------------------------------------------