Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.carno.net.au!harbinger.cc.monash.edu.au!munnari.OZ.AU!news.ecn.uoknor.edu!feed1.news.erols.com!howland.erols.net!news.mathworks.com!enews.sgi.com!news.be.com!news1.crl.com!nexp.crl.com!usenet From: "Jordan K. Hubbard" <jkh@FreeBSD.org> Newsgroups: comp.unix.bsd.freebsd.misc Subject: Re: The end of 2.1? Date: Tue, 18 Mar 1997 22:41:41 -0800 Organization: Walnut Creek CDROM Lines: 84 Message-ID: <332F8AA5.237C228A@FreeBSD.org> References: <332F180D.16E3@iphase.com> NNTP-Posting-Host: time.cdrom.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Mailer: Mozilla 3.01 (X11; I; FreeBSD 2.2-RELEASE i386) To: Dave Littell <dlittell@iphase.com> Xref: euryale.cc.adfa.oz.au comp.unix.bsd.freebsd.misc:37286 Dave Littell wrote: > - There's some kind of problem between 2.1.6 and the new > Solaris 2.5.1 DNS. After our Lab guys switched over to the new > DNS, NFS mounts hang and never complete. Switching back to the > previous DNS allows mounts to complete successfully. Other > machines using the new DNS can mount with no problems. Perhaps Solaris broke some backwards-compatibility mode; why not bring up a 2.2 test box (and don't tell me you don't have a test box, I don't even want to hear that from an ISP :) and see if the interoperability problems are still there? If so, it's easier for the maintainer to fix it in 2.2 then back-port it to 2.1. Despite reports to the contrary, the RELENG_2_1_0 branch (AKA -stable) is NOT dead and continues to receive updates. If you don't CTM or CVSup yourself to -stable, start and start right now. > - The latest and greatest NFS security problem: will this in Which specific NFS security problem are you talking about? "Latest and greatest" is too subjective to be informative. :) > - The previously discussed keyboard lockup problem manifests > itself more often than I'd really like (which is never). How many pieces of hardware does this occur on? I've never seen a keyboard lockup with 2.1.x on any of my machines, but then of course YMMV as always. It would be nice to narrow down the problem set, in any case. Have you filed a PR over this? > - The various ongoing battles with PPP - I'd love a 2.1 release > with all the fixes. Stick with -stable and you'll soon see enhancements to ppp trickle down. > - DHCP: I need something solid in 2.1. Since this is not something we bundle with the system, I can't comment. I don't even know which implementation it is you're attempting to use with 2.1. > - Gazing over the list of critical problems doesn't exactly > instill a deep sense of peace. Jeez, a filesystem problem over > 2 years old (kern/216)? Many of those are also stale and should have their statuses updated. Our new GNATsmeister is working as hard as he can to catch up with months of neglect - give him a chance. :) > - Endless install problems with the ports collection. Install > attempts either do nothing (gnat) or fail to compile due to You're probabably trying to use the -current ports collection which, as has been stated many many times already, is not for 2.1 users, never was and never will be. You need to stick with the ports collection which was bundled with 2.1, smaller as it may be. We don't have the resources to have it any other way, so don't even ask the obvious question, either. :) > What I'd like to grovel, plead, and beg for is an organized, > focused, and serious effort towards fixing the remaining known > problems in 2.1 and issuing enough maintenance CD releases to > ultimately get a 2.1.x that is truly "rock-stable". Yeah, I We've called numerous times to FreeBSD's user base to provide this kind of support, since we can either develop the product or we can hang back with the old versions. The 2nd tier support in a volunteer effort like this falls, therefore, to user-sponsored groups who take it upon themselves to maintain the old stuff. One of our developers, Warner Losh, has even publically volunteered to review & commit contributions to the 2.1-stable branch from users on several occasions. Guess how much response he got? I guess when it comes right down to it, users will always find it easier to enumerate problems and complain about them than actually do the work of fixing them. :-) > Whaddya think? I think you should subscribe to the -stable source track and start sending patches to Warner Losh. :-) -- - Jordan Hubbard FreeBSD core team / Walnut Creek CDROM.