diff --git a/en_US.ISO8859-1/books/faq/book.xml b/en_US.ISO8859-1/books/faq/book.xml index 411baf56e3..4ed1210014 100644 --- a/en_US.ISO8859-1/books/faq/book.xml +++ b/en_US.ISO8859-1/books/faq/book.xml @@ -4339,45 +4339,6 @@ kern.timecounter.hardware: TSC -> i8254 - - - Why is CVSup not integrated - in the main &os; tree? - - - - The &os; 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 &os; 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 &os; 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 &os; - 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 a package bundled on the &os; - installation CDs. - - However, &os; users are not without an integrated - CVSup compatible client anymore - since &os; 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). - - - I updated the sources, now how do I update my installed