On Fri, 20 Jan 2006 12:25:35 -0500
Douglas Wade Needham <cinnion@ka8zrt.com> wrote:

> a) The system does not update the HW clock.  Probably a known TODO,
>    but I get the following message when rebooting (which is no big
>    deal):
>=20
>     WARNING: clock lost 13016 days -- CHECK AND RESET THE DATE!
Yes, The HW clock is a TODO... For now you may set the HW clock via the
firmware menue.

> c) I have seen core dumps from newsyslog, sendmail, egrep and sshd.
[...]
>    I will probably be looking at these core files sometime in the next
>    week if I get a chance.
If you wane dig into this: GCC has code generation bugs in the hppa
backend. Somtimes it fails with "internal compiler error" or it
generates invalid assembler code. (This two errors are comon when cross
building on a LP64 host.) In these two cases compilation is aborted with
an error message. Somtimes the compiler siliently emits invalid code.
Sometimes resultig in a SIGILL, sometimes the code fails in verry
strange ways. You may be bitten by this. You can recompile the affected
programms with -O0, this may cure the problems with invalid code.

We should get GCC 4.x in the near future, maybe we are in luck and the
bugs are gone with 4.x.

> d) I now find myself wishing that we had X11. ;)  But I realize there
>    is still some other work to do, such as getting the HW clock
>    updating. ;)
... and many other things...

> e) At some point, we probably should think about updating the FAQs,
>    todos, release notes, etc.
Feel free to send patches to www@. ;-)
--=20


tsch=FC=DF,
       Jochen

Homepage: http://www.unixag-kl.fh-kl.de/~jkunz/