16.3. Using FreeBSD-stable

1. Join the FreeBSD-stable mailing list <freebsd-stable@FreeBSD.ORG> . This will keep you informed of build-dependencies that may appear in stable or any other issues requiring special attention. Developers will also make announcements in this mailing list when they are contemplating some contraversal fix or update, giving the users a chance to respond if they have any issues to raise concerning the proposed change. To join this list, send mail to <majordomo@FreeBSD.ORG> and say:

               subscribe freebsd-stable
   

   In the body of your message. Optionally, you can also say `help' and Majordomo will send you full help on how to subscribe and unsubscribe to the various other mailing lists we support.
2. Grab the sources from ftp.FreeBSD.ORG. You can do this in three ways:
   1. Use the CTM facility. Unless you have a good TCP/IP connection at a flat rate, this is the way to do it.
   2. Use the CMU sup program (Software Update Protocol). This is the second most recommended method, since it allows you to grab the entire collection once and then only what has changed from then on. Many people run sup from cron and keep their sources up-to-date automatically.
   3. Use ftp. The source tree for FreeBSD-stable is always "exported" on: ftp://ftp.FreeBSD.ORG/pub/FreeBSD/FreeBSD-stable

      We also use `wu-ftpd' which allows compressed/tar'd grabbing of whole trees. e.g. you see:

                  usr.bin/lex
      

      You can do:

                  ftp> cd usr.bin
                  ftp> get lex.tar.Z
      

      And it will get the whole directory for you as a compressed tar file.

3. Essentially, if you need rapid on-demand access to the source and communications bandwidth is not a consideration, use sup or ftp. Otherwise, use CTM.
4. Before compiling stable, read the Makefile in /usr/src carefully. You should at least run a `make world' the first time through as part of the upgrading process. Reading the FreeBSD-stable mailing list <freebsd-stable@FreeBSD.ORG> will keep you up-to-date on other bootstrapping procedures that sometimes become necessary as we move towards the next release.