gnubeep 1.4 BUGS


No known bugs in gnubeep-1.4.  I have taken every care to ensure that there 
are no bugs or security issues in gnubeep, but there might be.  I also test
gnubeep for manifesting bugs before each release, but I haven't found any.

After the release of gnubeep 1.2, Andrew <colliera@ukzn.ac.za> reported that
compile errors/warnings can occur on some Linux systems, due to some non-
standard code.  This release fixes those potential compile difficulties.

Also, Raik Lieske reported my mistake in the main() function.  I had used a
getuid() call to check for the UID of the invoking user being root, and if
they weren't, gnubeep exited.  However, even if gnubeep was SUID root, gnubeep
would still exit because of this.  A major "DUH!" on my part ;-)

gnubeep 1.3 still had several inconsistancies with following the C standards.
Older versions of gcc (2.x?) would complain and bail when they came across 
this code.  Andrew B. Collier suggested a fix for this, enabling slightly older
releases of gcc to build gnubeep successfully.


Please email me bug reports to <shaunige@yahoo.co.uk> :-).


Thank you :-)



Shaun Colley - 
<shaunige@yahoo.co.uk>
