Date: Sun, 08 Oct 2000 22:58:21 GMT From: Salvo Bartolotta <bartequi@inwind.it> To: media@ct1.nai.net, freebsd-questions@FreeBSD.ORG Subject: Switching one's sources between branches and/or dates & bad144 (was Re: obtaining partition information??) Message-ID: <20001008.22582100@bartequi.ottodomain.org> References: <78803519@toto.iv> <v03130302b6061e99ae94@[209.150.34.212]>
next in thread | previous in thread | raw e-mail | index | archive | help
>>>>>>>>>>>>>>>>>> Original Message <<<<<<<<<<<<<<<<<<
On 10/8/00, 6:01:26 PM, media@ct1.nai.net wrote regarding Re:
obtaining partition information??:
> Hmmm . . I think I need to find out exactly when bad144 was removed,
> and not upgrade past that point. Unfortunately, my hard drive has bad=
> blocks according to FreeBSD (they were undetectable using DOS), so
> until I buy a new hard drive, I think I need to keep bad144.
From /usr/src/UPDATING:
<blockquote>
19991203:
BAD144 support has been removed. Cope or replace the
hardware.
</blockquote>
You may wish to take a look at cvsup(1), notably at the "date" item;
which will allow you to update your system exactly to the desired
date. Please have a look at the cvsup FAQ at http://www.polstra.com.
More generally, the following "theoretical" considerations may be of
interest:
<CONSIDERATION I>
<REMARK>
If one specifies tag=3DA in a supfile, cvsup will generate a checkouts
file called "checkouts.cvs:A": e.g. if tag=3DRELENG_4, a checkouts
file called checkouts.cvs:RELENG_4 is generated.
</REMARK>
When tracking FreeBSD src-all, if one wishes to switch from tag=3DA to
tag=3DB (A<B or A>B does not make any difference), and if one's
checkouts file is, say, checkouts.cvs:A, the following steps need
to be performed:
1) mv checkouts.cvs:A checkouts.cvs:B
/* This will provide the subsequent step with the appropriate
checkouts file */
2) write a supfile whose collection line reads:
src-all tag=3DB
3) cvsup sources (ie src-all) using the supfile as per 2).
Cvsup will look for a checkouts.cvs:B -- in that the target is B;
thus, cvsup will make use of the information contained therein in
order to correctly manage the sources. The benefits:
a) the sources are dealt with correctly (no stale files, no disk space
wasted);
b) less load is placed on the server in that cvsup will operate in the
most efficient way.
Example I
A=3DRELENG_4, B=3D.
The period in "B=3D." means CURRENT.
This is a rather typical update, from 4-STABLE to -CURRENT.
Example II
A=3D. B=3DRELENG_4.
This is the reverse operation, from -CURRENT to 4-STABLE.
</CONSIDERATION I>
<CONSIDERATION II>
If one wishes to switch from "tag=3DA" to "tag=3DA" as of a different GM=
T
date (say, "date=3DD"), one will perform the following actions:
1) write a supfile whose collection line reads:
src-all tag=3DA date=3DD
2) cvsup using the supfile as per 1)
The fact that the date is < or > the date of the last update with tag=3D=
A
is immaterial.
For example, in order to specify the date "August 27, 2000, 10:00:00
GMT" one will write the line:
src-all tag=3DRELENG_4 date=3D2000.08.27.10.00.00
N.B. The format of the date is rigid. One has to specify all the
components of a date: century (19 for the 19th or 20 for the 20th),
year, month, day, hour, minutes, seconds -- as shown in the above
example. For more information, please see cvsup(1).
<REMARK>
Whether or not a date is specified, the checkouts file will be called
checkouts.cvs:A (eg checkouts.cvs:RELENG_4). As a result, no
particular action is needed in order to revert to the previous state:
one has to modify the date in the supfile, and csvup again.
</REMARK>
</CONSIDERATION II>
Best regards,
Salvo
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20001008.22582100>