On 9 Nov 99, at 14:42, Steinar H. Gunderson wrote:
> The problem seems to be that mprime is compiled to glibc 2.1, while RH 4.2
> uses... libc5? glibc 2.0? glibc 2.1 (even in static version) needs some
> special files to operate. This has been discussed on the list before, and
> perhaps it's time to fix it :-)
I tend to agree... Actually someone (George?) put up mprime & sprime
v19.1 over the weekend, which (according to the whatsnew file) has a
workaround coded in - though I'm unable to check whether it works,
since I've not had problems with v19.0 on any of my systems.
> I could perhaps download and compile glibc 2.1, and compile it with static NSS.
> Then I could compile mprime (perhaps I'll need George's security.c and
> security.h, but that's another matter entirely -- we'll take that when it
> comes) with a version that would work for non-2.1 users. Any protests?
Would it be reasonable to suggest instead that someone build sprime
v19.x on a system running RH 4.x, or something else old enough that
the dynamic library problem hadn't been invented? Or does that
replace one problem with another, viz. a binary that won't run on
current releases?
I don't think there is any other significant issue ... ???
>
> For now, you could revert to v18, use v18 only to report your results, report
> them via the manual forms, or just wait for us to do something about it :-)
Reverting to v18 - you'll lose any work in progress & have to restart
it from scratch 8-(
Using v18 to report results - there would seem to be scope for
confusion here - messy! 8-(
Reporting via manual forms - sounds OK for a few systems that are
relatively easily "got at", but unmanageable for large numbers of
systems - especially if they don't have a web browser available. Also
will cause loss of PrimeNet credit 8-(
Just wait - I think we could & should get something done about this
PDQ.
One possible option would be to archive the v19 save file(s), stop
v19, remove the current assignment from worktodo.ini (by deleting the
top line in the file) and restart using v18 for the time being. When
a fixed v19 becomes available, replace the save file(s) & the
worktodo.ini entry for the assignment. This will preserve work in
progress, though the credit will obviously be deferred.
Also the option of upgrading to a new version of linux should be
considered. The cost is not great (get the CheapBytes CD for less
than $5), though there may be an issue with disk space on some
systems - linux bloats too, though by no means as badly as windoze!
The point here is that there are a number of security problems
(especially in sendmail and the ftp daemon) which need attention;
upgrading to a recent release is a reasonably convenient way of
fixing these. Though note that RH 6.0 _still_ needs wu-ftpd upgraded;
everything prior to v2.6.0 is vulnerable, and hackers are actively
scanning IP address space looking for systems running wu-ftpd v2.5.x.
Regards
Brian Beesley
_________________________________________________________________
Unsubscribe & list info -- http://www.scruz.net/~luke/signup.htm
Mersenne Prime FAQ -- http://www.tasam.com/~lrwiman/FAQ-mers
