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!fu-berlin.de!irz401!orion.sax.de!uriah.heep!news From: j@uriah.heep.sax.de (J Wunsch) Newsgroups: comp.unix.bsd.freebsd.misc Subject: Re: Walnut Creek CDROMs behind times Date: 14 Dec 1996 00:35:43 GMT Organization: Private BSD site, Dresden Lines: 66 Message-ID: <58ssov$jti@uriah.heep.sax.de> References: <57u2s8$9ac@news.ziplink.net> Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) NNTP-Posting-Host: localhost.heep.sax.de Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Newsreader: knews 0.9.6 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Xref: euryale.cc.adfa.oz.au comp.unix.bsd.freebsd.misc:32556 mi@rtfm.ziplink.net (Mikhail Teterin) wrote: > I do not know why it takes Walnut Creek _6_ weeks to get the > subscritption CDROM to me. The technological process, etc. Well, a newsgroup is probably not the best place to ask about a companie's policy. Why didn't you ask their salespeople? > 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). Upgrading /usr/src is sufficient, yes, you only gotta `make world' afterwards. Of course, files in /etc won't touched, and must be merged manually. Providing a diff between one snapshot and the next will be far off from becoming 100 % reliable. Remember, unlike releases, the SNAPs are just being checked out from the tree at some point in time, but they are being checked out from a moving target -- there's no guarantee that the CVS repository isn't already being changed while the checkout of the source is in progress. > 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... No. Client-side CVS is indeed very simple to set up: all you need is setting a single environmental variable, CVSROOT, to point to the root of your CVS tree. The SNAP CD-ROMs come with a fully populated CVS tree, all you need is copying it over to the disk. (Sorry, you can't use it directly from the CD since cvs wants to be able to write lock files into the tree while checking them out.) Then, simply nuke your /usr/src, and do: setenv CVSROOT /where/it/lives cd /usr cvs co src cd src make world Now tell me this is more complicated than setting up Apache or Samba... :-) NB: /where/it/lives should just have subdirectories named `CVSROOT', `src', `tools', and if you want `ports'. Don't accidentally set the $CVSROOT variable to /where/it/lives/CVSROOT, despite of its name! > -mi (who is afraid the 2.1.6 CDROM will > show up after 2.2 is FTPable) This is not unlikely at all. If FreeBSD 2.2 is something for you, then FreeBSD 2.1.6 most likely isn't. While making the schedules for 2.1.6 and 2.2, we even thought about releasing both at the same point in time, and asking Walnut Creek to release them as a 4 CD version. (It only didn't happen since 2.1.6 proved to be a little less work to get it ready than 2.2 turned out to be now.) Both releases are targeted for a very different set of users. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-)