Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.carno.net.au!harbinger.cc.monash.edu.au!munnari.OZ.AU!spool.mu.edu!uwm.edu!math.ohio-state.edu!howland.erols.net!cam-news-hub1.bbnplanet.com!news.bbnplanet.com!cpk-news-hub1.bbnplanet.com!news.mindspring.com!mindspring!uunet!in3.uu.net!199.232.240.5!news.ziplink.net!rtfm.ziplink.net!mi From: mi@rtfm.ziplink.net (Mikhail Teterin) Newsgroups: comp.unix.bsd.freebsd.misc Subject: Walnut Creek CDROMs behind times Date: 2 Dec 1996 08:09:44 GMT Organization: Aldan at Newton Upper Falls Lines: 30 Message-ID: <57u2s8$9ac@news.ziplink.net> Reply-To: mi@ALDAN.zipnet.net NNTP-Posting-Host: 199.232.255.52 Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Newsreader: knews 0.9.8 I do not know why it takes Walnut Creek _6_ weeks to get the subscritption CDROM to me. The technological process, etc. But I know the unpleasent feeling of getting something that's obsolete -- the next snapshot or even Release is usually out there in less then 6 weeks. One solution would be to slow down the development (no, thanks). The other solutions I see, is to have the prelast2last patches available on the ftp.freebsd.org mirrors and make install software offer an option of checking them out and upgrading the installed system components if neccessary. I do realize, that binaries are rebuilt completely, but there is a dependency list. The list can tell which binaries should go into the "patch" by checking for changes in the sources. And, of course, plain upgrading of /usr/src should not require the whole power (and thus, complexity) of cvs. (Please, tell me it is possible already). The third solution would be to insist on using cvs, but then, I'd suggest putting it's set-up into the sysinstall -- IMHO, it is way more complicated then SAMBA or Apache set-up... -mi (who is afraid the 2.1.6 CDROM will show up after 2.2 is FTPable) -- "Windows for dummies"