On Tue, 9 Jan 2007, Jacques Klein wrote:
> I am using mon-1.1.0pre1 ($Id: mon,v 1.10 2004/11/15 14:45:16 vitroth
> Exp $) and
> would like to know what is the "currently stable release" and also the
> "hopefully still under developpement release".
> Can it be considered safe to upgrade from release 1.10 to release 1.22
> from CVS ?
i wonder if vitroth will beat me to this :)
the latest stable version of mon and mon-client are tagged in cvs as
mon-1-2-0 and mon-client-1-2-0, respectively. these are safe to use.
to get it from cvs on sourceforge, do this:
export CVSROOT=":pserver:[EMAIL PROTECTED]:/cvsroot/mon"
cvs login
(hit enter)
mkdir mon
cd mon
cvs -z3 export -d mon-1-2-0 -r mon-1-2-0 mon
cvs -z3 export -d mon-client-1.2.0 -r mon-client-1-2-0 mon-client
that should get you going.
here're a couple of tidbits on cvs:
you can't judge the version by the cvs version tag in the "mon", because
that is just one file, and a full release is a laundry list of all the
various files in the distro. the "release", such as 1.2.0, is given a
tag in cvs, which associates a set of files with specific versions
into the "release".
if you look at the cvs browser on sourceforge
(http://mon.cvs.sourceforge.net/mon/) you can choose a module ("mon")
and then it'll show you the tag names for the branches and the other
non-branch tags. so what you can do is specify a branch tag when you do
a cvs checkout if you want the latest non-released "devel" version for
a particular branch, or you can specify a release tag (not a branch
tag). in the above example, mon-1-2-0 was the non-branch tag.
mon-1-2-branch is the latest stable branch, and this is to be paired with
mon-client-1-2-branch in the "mon-client" module.
_______________________________________________
mon mailing list
mon@linux.kernel.org
http://linux.kernel.org/mailman/listinfo/mon
