Because it's an *old* server, and because 5.4-r should be a mature enough distribution by now that any bugs which were going to be fixed would already be fixed.
I could only find one reference to a problem like this one, and in that case it was happening in 6.x, which indicates that whatever the problem is, it hasn't been fixed. Which implies that it's either considered to be not a problem by way of an easy workaround, or that it's not an important problem due to not happening very often. Either way, an answer to the question at hand would be much appreciated. --- Kris Kennaway <[EMAIL PROTECTED]> wrote: > On Wed, Apr 04, 2007 at 03:00:34PM -0400, m yelle > wrote: > > I'm attempting to install 5.4-r on an old server > which > > has been running 4.9-stable for the last few years > > without any problems, with longest uptime of just > over > > 6 months. I'm installing to a tested clean/blank > scsi > > hdd. > > Why are you installing a version of FreeBSD that is > nearly 2 years > old? How about trying modern versions before > writing off FreeBSD on > your hardware:) > > Kris > __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com _______________________________________________ firstname.lastname@example.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"