Jerry wrote: > Really ... > Hi, I am a FreeBSD user, and I would like to report a problem that doesn't > exist. I have a theoretical solution for this unknown problem, but I cannot > test it because I cannot create the environment. > > Seriously, there are plenty of real problems. Attempting to anticipate > theoretical ones and then devise hypothetical solutions is a job best left > to those working on quantum physics. > > That's a little unfair (but I get your point) .. in this case though noting comments everywhere this is not something unknown - it was known that :T -> :tu would break the old make and it was also known for sometime when it would happen (comments elsewhere in this months archives say the change was postponed until 8.3 went EOL - so advance warning would have been possible (in this case)... and that should have been easy by performing a make version check... ( http://lists.freebsd.org/pipermail/freebsd-questions/2010-October/222214.html )
Not meaning this to beat Baptiste... but yes it could have been handled better - and this is not the first time - I have 30 production servers stuck on 6.1 because when FreeBSD got to a certain level (7.3?) the same thing happened... Security issues you cry!? Not an issue - they are firewalled and the software on them (exception the base OS) has no CVE's (or didn't at the time) for the options compiled and used... sure the base OS might have vulnerabilities, but if anyone gets through the application gateway to a root prompt to be able to exploit those issues I have many serious problems that a "skipt kiddie" with root will be one of the least of the issues.. Michelle -- Michelle Sullivan http://www.mhix.org/ _______________________________________________ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
