> > Is your 7.2 totally 'up2date -u'?
> No -- fresh install from a 7.2 CD set.  No other updates.

You probably should at least consider updating 7.2 with all of the RedHat
errata packages.  RedHat 9.0 was released this week, and RedHat 7.0 and
older are officially end-of-lifed immediately.  7.2 is not far from being
"too old" to support.  RedHat 8.0 is probably worth the download time, since
it's free.  Find a fast mirror and have at it!  :-)

There's a very good chance that the bug is NOT in Eagle -- there has been a
lot of work on X itself since RH 7.2-era original packages were released.
Same thing with Glibc underlying C libraries.  Tons of changes.  Upgrading a
raw 7.2 installation even with an automated tool like up2date and a free
RedHat Network account is relatively painful these days.  (And RHN is turned
off for free users right now, since their servers are under extreme load due
to the RH 9.0 release.)

> I'm evaluating Linux and various distribs of it to see if I should
> completely move over from Win2k.  There is no personal data on these
> "experiment" partitions, so it's fine with me.  And I won't move over
> until I sort out these bugs like Eagle crashing.

That's ultra-safe... but one crash does not make an unstable application.
At least with Linux you can stack trace the application with free tools if
it's misbehaving and see where it dies.  Also the graphical environment is
not integrated into the system so completely that you can't kill it
(usually) and restart it without a reboot.

I regularly work on machines that have been up (not saying this is good, I'd
rather upgrade them but...) for 3 years without a reboot running Linux.
None of them run graphical applications however... they're all servers.  No
need for X on a server.

Nate Duehr, nate@natetech.com

--
http://www.piclist.com#nomail Going offline? Don't AutoReply us!
email listserv@mitvma.mit.edu with SET PICList DIGEST in the body