Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.carno.net.au!harbinger.cc.monash.edu.au!news.mira.net.au!news.vbc.net!vbcnet-west!garlic.com!uunet!in1.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: Re: Walnut Creek CDROMs behind times
Date: 19 Dec 1996 07:22:47 GMT
Organization: Aldan at Newton Upper Falls
Lines: 69
Message-ID: <59aqg7$ecf@news.ziplink.net>
References: <57u2s8$9ac@news.ziplink.net> <58ssov$jti@uriah.heep.sax.de>
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
Xref: euryale.cc.adfa.oz.au comp.unix.bsd.freebsd.misc:32791
Honorable J Wunsch
wrote on 14 Dec (in article <58ssov$jti@uriah.heep.sax.de>):
>> 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?
Joerg! Show me a single question mark in the parageaph you quote... :)
=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.
Well, what gets burned onto a CDROM is not a moving target, is it?
Long before the CDROM is created and arived to my house the target
is shot and immobilized. What I was talking about was a way of knowing
which of the binary pieces *.?? I need to download to be able
to install the LATEST snapshot/Release from the local disk.
Or may be to make the installation program smart enough to be able
to get the updated pieces from another location... Say,
ftp.freebsd.org:/pub/FreeBSD/5.0RELEASE-5.1RELEASE-DELTAS/bin.aa
ftp.freebsd.org:/pub/FreeBSD/5.0RELEASE-5.1RELEASE-DELTAS/bin.ab
ftp.freebsd.org:/pub/FreeBSD/5.0RELEASE-5.1RELEASE-DELTAS/bin.ac
They will be parts of one bin.tar.gz which will contain the modified
binaries. Install will get them after the original bin.?? is installed
before finishing the whole installation.
=Then, simply nuke your
=/usr/src, and do:
= setenv CVSROOT /where/it/lives
= cd /usr
= cvs co src
= cd src
= make world
This will probably give the latest aka moving target. What about a
particular version? Like 2.1.6-RELEASE ?
=.......................................................... Don't
=accidentally set the $CVSROOT variable to /where/it/lives/CVSROOT,
=despite of its name!
Just this last note makes it somewhat tricky...
>> -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.
It is. I want 2.2 at home and 2.1.6 at work, where it has to demonstrate
rock-solid stability to the stupid NT machines near-by.
Still, with the unlikely to change situation of CDROMs arriving outdated
something easier then full cvs and ``make world'' seems necessary.
-mi
--
"Windows for dummies"