diff --git a/en_US.ISO8859-1/books/faq/book.sgml b/en_US.ISO8859-1/books/faq/book.sgml index 9791952eb6..525fe4bf2c 100644 --- a/en_US.ISO8859-1/books/faq/book.sgml +++ b/en_US.ISO8859-1/books/faq/book.sgml @@ -4412,25 +4412,36 @@ kern.timecounter.hardware: TSC -> i8254 - Why is CVSup not integrated in the main FreeBSD tree? + Why is CVSup not integrated in the main FreeBSD tree? - The FreeBSD base system is designed as self-hosting - it + The FreeBSD base system is designed as self-hosting — it should be possible to build the whole operating system starting with a very limited set of tools. Thus, the actual build tools needed to compile the FreeBSD sources are bundled with the sources themselves. This includes a C compiler (&man.gcc.1;), &man.make.1;, &man.awk.1;, and similar tools. - Since CVSup is written in Modula-3, adding it to the FreeBSD + Since CVSup is written in Modula-3, adding it to the FreeBSD base system would also require adding and maintaining a Modula-3 compiler. This would lead to both an increase in the disk space consumed by the FreeBSD sources and additional maintenance work. Thus, it is much easier for both the developers and users to - keep CVSup as a separate port, which can be easily installed as + keep CVSup as a separate port, which can be easily installed as a package bundled on the FreeBSD installation CDs. + + However, &os; users are not without an integrated + CVSup compatible client anymore + since FreeBSD 6.2-RELEASE. Thanks to &a.mux;, + CVSup was rewritten in C as + &man.csup.1; and it is the part of the base system by now. + Although it does not implement all the features of + CVSup at the moment, it is good + enough (and really fast!) to keep your sources synchronized. + For systems earlier than 6.2, it can be installed as a port + or package (see net/csup).