CVS

The script I am using for updating my own website(s) is not quite complex, it is here:

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14

#!/bin/sh
# Detect and update the files
#
# $Phantasm$

CVSROOT="/home/ncvs"
SUPFILE="/home/delphij/cvsup/supfile-delphijweb"
LOCKFILE="/home/delphij/cvsup/cvsup-lock"

if [ -f ${CVSROOT}/CVSROOT/commitlogs/have_updates ]
then
	rm ${CVSROOT}/CVSROOT/commitlogs/have_updates
	cvsup -1gL 2 ${SUPFILE}
fi

Of course you need some CVSROOT scripts to get it work, but the idea is not too complex.

Sometimes CVS is very nasty when operating. For example, when you want to remove a whole tree (including zillion sub-directories and files) you may have to enter commit log (at least, confirm) for every directory, if you are going to do a “cvs ci” in the top level directory.

It is possible to solve this problem with simple Unix(R) commands:

David O’Brien has gave me the FreeBSD 1.x CVS Repository and I have set up a CVSWeb view for it so it will be easy to read the code/changes.

FreeBSD 1.x was forbidden and supposed to be destroyed in May 1994, because the lawsuit of USL against BSDI, UC Berkeley, and the FreeBSD/NetBSD projects. Today, as 32V and some code in the same time was released under BSD License, it is legal to keep the repo again.

FreeBSD 1.x is based on 4.3 BSD, while FreeBSD 2.x and later are based on 4.4BSD-Lite2. The historical archive, is valuable for anyone who interested in the Operating System itself, its development, and more.

今天说实在的没有做什么，但是觉得很累，大概是昨天晚上没有睡好的原因。

晚上回了趟学校，解决了一个非常糟糕的cvs问题——这再次体现了一个很重要的原则，除非你是guru，否则出了问题别自己找辙workaround——由于某个committer在放飞repository里面自己试图workaround一个自己不了解原因的问题，导致我不得不花了将近一个小时的时间去解决它……

其实我也应该workaround的——很简单，删掉那些错误的rcs文件了事，因为那个committer写的log一直不怎么合要求，但是最后还是决定祭出大招——和cvs大战。

应该这么做么？或者，不应该这么做么？

With alu@’s help, we have cvs.freebsd.org.cn online again! I have set up the CNPROJ branch in a similiar manner as `delphijfork'.

CNPROJ will then work under this branch. Later merge/commits will utilize another tag: CNPROJ_COMMITTED.

Top ten established HTTP connection from IP to our box: (IP=127.0.0.1)

netstat -na | grep “127\.0\.0\.1\.80 " | grep ESTABLISHED | cut -c43- |cut -f1-4 -d’.’ | sort | uniq -c | sort -nr | head -10

Merge FreeBSD-CURRENT changes to delphijfork:
retag `cvs -d /home/fcvs rdiff -rHEAD -rDELPHIJ_FORK_LASTMERGE src | grep Index: | awk ‘{print $2;}’ | grep src`

I think FreeBSD will soon release a new advisory. Simply put, cvs updated again and is vulnerable to some potential security risks.

I have noticed that today’s cvsup brings this to my local repo: src/sys/kern/kern_kse.c. From the version it seems to be from kern_thread.c. Waiting commitmail to explain this.

It seems (still can’t access to the Internet right now, however, HTTP and cvsup works) that OpenBSD has imported gdb 6.1 into their source tree. I am not sure whether they did some hacks to the source repository (from cvsup result, there is not), but the result is really strange. It seems that the last import was done by using a “cvs add -rCYGNUS” and not “cvs import”…

I hope FreeBSD can import a newer gdb ASAP, as well as gcc 3.4 series.

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31

des         2004/05/18 23:40:52 PDT

  FreeBSD src repository

  Modified files:        (Branch: RELENG_4_7)
    .                    UPDATING 
  Modified files:        (Branch: RELENG_4_8)
    .                    UPDATING 
  Modified files:        (Branch: RELENG_4_9)
    .                    UPDATING 
  Modified files:        (Branch: RELENG_5_0)
    .                    UPDATING 
  Modified files:        (Branch: RELENG_5_1)
    .                    UPDATING 
  Modified files:        (Branch: RELENG_5_2)
    .                    UPDATING 
  Modified files:        (Branch: RELENG_4_7)
    sys/conf             newvers.sh 
  Log:
  Bump and document patch level.
  
  Approved by:    so
  
  Revision        Changes    Path
  1.73.2.74.2.31  +3 -0      src/UPDATING
  1.73.2.80.2.24  +3 -0      src/UPDATING
  1.73.2.89.2.9   +3 -0      src/UPDATING
  1.229.2.27      +3 -0      src/UPDATING
  1.251.2.19      +3 -0      src/UPDATING
  1.282.2.15      +3 -0      src/UPDATING
  1.44.2.26.2.29  +1 -1      src/sys/conf/newvers.sh

很想知道是怎么commit的……