> Check the mailing list archives around 4.3-RELEASE, when it was > discovered that /etc/pam.conf didn't get "ssh" lines added to it > on upgrades, and people were getting locked out of boxes left and > right (predates "other" entries). > > Changing behaviour on an upgrade, without the user's consent, is > a bad thing (note: *consent*, not *knowledge*: it's not up to the > user to know about everything some programmer has diddled into > non-operability in the two years since FreeBSD 5.x was branched).
Isn't that what UPDATING is for and wouldn't between 4.x and 5.x be better than 5.x and 5.x+n? -- David W. Chapman Jr. [EMAIL PROTECTED] Raintree Network Services, Inc. <www.inethouston.net> [EMAIL PROTECTED] FreeBSD Committer <www.FreeBSD.org> To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
