5.5. Checking Out Source Code

• Device Mapper library and tools

  The device mapper library is required to build LVM 2.

  The first time you download from cvs, you must login

  # cvs -d :pserver:cvs at sources.redhat.com:/cvs/dm login cvs

  The password is `cvs'. The command outputs nothing if successful and an error message if it fails. Only an initial login is required. All subsequent CVS commands read the password stored in the file $HOME/.cvspass for authentication.

  Use the following to check out a copy of the code

  # cvs -d :pserver:cvs at sources.redhat.com:/cvs/dm checkout device-mapper

  This will create a new directory device-mapper in your current directory containing the latest, up-to-the-minute device mapper code.

• LVM 2

  The first time you download from cvs, you must login

  # cvs -d :pserver:cvs at sources.redhat.com:/cvs/lvm2 login cvs

  The password is `cvs'. The command outputs nothing if successful and an error message if it fails. Only an initial login is required. All subsequent CVS commands read the password stored in the file $HOME/.cvspass for authentication.

  Use the following to check out a copy of the code

  # cvs -d :pserver:cvs at sources.redhat.com:/cvs/lvm2 checkout LVM2

  This will create a new directory LVM2 in your current directory containing the latest, up-to-the-minute LVM 2 code.

• LVM 1

  The first time you download from cvs, you must login

  # cvs -d :pserver:cvs at sources.redhat.com:/cvs/lvm login cvs

  The password is `cvs'. The command outputs nothing if successful and an error message if it fails. Only an initial login is required. All subsequent CVS commands read the password stored in the file $HOME/.cvspass for authentication.

  Use the following to check out a copy of the code

  # cvs -d :pserver:cvs at sources.redhat.com:/cvs/lvm checkout LVM

  This will create a new directory LVM in your current directory containing the latest, up-to-the-minute LVM 1 code.

CVS commands work from anywhere inside the source tree, and recurse downward. So if you happen to issue an update from inside the `tools' subdirectory it will work fine, but only update the tools directory and it's subdirectories. In the following command examples it is assumed that you are at the top of the source tree.