From 9145ff93b548d5004bffcb289ab9b47323ae135f Mon Sep 17 00:00:00 2001 From: Dru Lavigne Date: Wed, 12 Feb 2014 21:31:34 +0000 Subject: [PATCH] White space fix only. Translators can ignore. Sponsored by: iXsystems --- .../books/handbook/mirrors/chapter.xml | 491 ++++++++++-------- 1 file changed, 262 insertions(+), 229 deletions(-) diff --git a/en_US.ISO8859-1/books/handbook/mirrors/chapter.xml b/en_US.ISO8859-1/books/handbook/mirrors/chapter.xml index 154047650d..910ccad7ee 100644 --- a/en_US.ISO8859-1/books/handbook/mirrors/chapter.xml +++ b/en_US.ISO8859-1/books/handbook/mirrors/chapter.xml @@ -28,7 +28,8 @@ Phone: +1 925 240-6652 Fax: +1 925 674-0821 Email: info@freebsdmall.com - WWW: http://www.freebsdmall.com/ + WWW: http://www.freebsdmall.com/ @@ -39,7 +40,8 @@ D-81371 München Germany Phone: (0177) 428 419 0 - WWW: http://www.hinner.de/linux/freebsd.html + WWW: http://www.hinner.de/linux/freebsd.html @@ -50,7 +52,8 @@ Margate CT9 2TB United Kingdom - WWW: https://linux-distro.co.uk/ + WWW: https://linux-distro.co.uk/ @@ -63,7 +66,8 @@ United Kingdom Phone: +44 (0)247 615 8121 Fax: +44 1491 837016 - WWW: http://www.linuxemporium.co.uk/products/bsd/ + WWW: http://www.linuxemporium.co.uk/products/bsd/ @@ -76,7 +80,8 @@ Russia Phone: +7-812-3125208 Email: info@linuxcenter.ru - WWW: http://linuxcenter.ru/shop/freebsd + WWW: http://linuxcenter.ru/shop/freebsd @@ -87,26 +92,28 @@ <acronym>FTP</acronym> Sites The official sources for &os; are available via anonymous - FTP from a worldwide set of mirror sites. The site - ftp://ftp.FreeBSD.org/pub/FreeBSD/ is well - connected and allows a large number of connections to it, but - you are probably better off finding a closer - mirror site (especially if you decide to set up some sort of - mirror site). + FTP from a worldwide set of mirror sites. + The site ftp://ftp.FreeBSD.org/pub/FreeBSD/ + is well connected and allows a large number of connections to + it, but you are probably better off finding a + closer mirror site (especially if you decide to + set up some sort of mirror site). - Additionally, &os; is available via anonymous FTP from the - following mirror sites. If you choose to obtain &os; via - anonymous FTP, please try to use a site near you. The mirror - sites listed as Primary Mirror Sites typically - have the entire &os; archive (all the currently available - versions for each of the architectures) but you will probably - have faster download times from a site that is in your country - or region. The regional sites carry the most recent versions - for the most popular architecture(s) but might not carry the - entire &os; archive. All sites provide access via anonymous FTP - but some sites also provide access via other methods. The - access methods available for each site are provided in - parentheses after the hostname. + Additionally, &os; is available via anonymous + FTP from the following mirror sites. If you + choose to obtain &os; via anonymous FTP, + please try to use a site near you. The mirror sites listed as + Primary Mirror Sites typically have the entire + &os; archive (all the currently available versions for each of + the architectures) but you will probably have faster download + times from a site that is in your country or region. The + regional sites carry the most recent versions for the most + popular architecture(s) but might not carry the entire &os; + archive. All sites provide access via anonymous + FTP but some sites also provide access via + other methods. The access methods available for each site are + provided in parentheses after the hostname. &chap.mirrors.ftp.index.inc; @@ -123,8 +130,8 @@ CVS has been deprecated by the project, and its use is - not recommended. - Subversion + not recommended. Subversion should be used instead. @@ -138,44 +145,44 @@ CTM is a method for keeping a - remote directory tree in sync with a central one. It is built into &os; - and can be used to synchronize a system with &os;'s source repositories. - It supports synchronization of an entire repository or just the specified branches. + remote directory tree in sync with a central one. It is built + into &os; and can be used to synchronize a system with &os;'s + source repositories. It supports synchronization of an entire + repository or just the specified branches. - CTM is specifically designed for use on - lousy or non-existent TCP/IP connections. It provides the ability - for changes to be automatically sent by email. It requires the user - to obtain up to three deltas per day for the most active - branches. Update sizes are always kept as - small as possible and are typically less than 5K. About one in very ten - updates is 10-50K in size, and there will occasionally be an update - larger than 100K+. + CTM is specifically designed for + use on lousy or non-existent TCP/IP connections. It provides + the ability for changes to be automatically sent by email. It + requires the user to obtain up to three deltas per day for the + most active branches. Update sizes are always kept as small as + possible and are typically less than 5K. About one in very ten + updates is 10-50K in size, and there will occasionally be an + update larger than 100K+. - When using CTM to track &os; development, - refer to the - caveats related to working directly from the development - sources rather than a pre-packaged release. These are discussed - in Tracking a Development Branch. + When using CTM to track &os; + development, refer to the caveats related to working directly + from the development sources rather than a pre-packaged release. + These are discussed in Tracking + a Development Branch. - Little documentation exists on - the process of creating deltas or using CTM - for other purposes. Contact the - &a.ctm-users.name; mailing list for questions on using - CTM. + Little documentation exists on the process of creating + deltas or using CTM for other + purposes. Contact the &a.ctm-users.name; mailing list for + questions on using CTM. Getting Deltas The deltas used by CTM can be obtained either through - anonymous FTP or - email. - - FTP deltas can be obtained from the following mirror sites. - When using anonymous FTP to obtain CTM deltas, - select a geographically close mirror. - In case of problems, contact the &a.ctm-users.name; - mailing list. + anonymous FTP or email. + + FTP deltas can be obtained from the + following mirror sites. When using anonymous + FTP to obtain + CTM deltas, select a geographically + close mirror. In case of problems, contact the + &a.ctm-users.name; mailing list. @@ -184,10 +191,12 @@ - ftp://ftp.FreeBSD.org/pub/FreeBSD/development/CTM/ + ftp://ftp.FreeBSD.org/pub/FreeBSD/development/CTM/ - ftp://ftp.FreeBSD.org/pub/FreeBSD/CTM/ + ftp://ftp.FreeBSD.org/pub/FreeBSD/CTM/ @@ -199,7 +208,8 @@ - ftp://ftp.za.FreeBSD.org/pub/FreeBSD/CTM/ + ftp://ftp.za.FreeBSD.org/pub/FreeBSD/CTM/ @@ -211,99 +221,97 @@ - ftp://ctm.tw.FreeBSD.org/pub/FreeBSD/development/CTM/ + ftp://ctm.tw.FreeBSD.org/pub/FreeBSD/development/CTM/ - ftp://ctm2.tw.FreeBSD.org/pub/FreeBSD/development/CTM/ + ftp://ctm2.tw.FreeBSD.org/pub/FreeBSD/development/CTM/ - ftp://ctm3.tw.FreeBSD.org/pub/FreeBSD/development/CTM/ + ftp://ctm3.tw.FreeBSD.org/pub/FreeBSD/development/CTM/ - To instead receive deltas through email, subscribe to one of the - ctm-src distribution lists available from - http://lists.freebsd.org/mailman/listinfo. For example, - &a.ctm-src-cur.name; supports the HEAD of the development - branch and &a.ctm-src-9.name; supports the 9.X release branch. + To instead receive deltas through email, subscribe to one + of the ctm-src distribution lists available + from http://lists.freebsd.org/mailman/listinfo. + For example, &a.ctm-src-cur.name; supports the HEAD of the + development branch and &a.ctm-src-9.name; supports the 9.X + release branch. - As - CTM updates arrive through email, - use ctm_rmail to unpack and - apply them. This command can be run directly from an entry in - /etc/aliases in order to - automate this process. Refer to - &man.ctm.rmail.1; for more - details. + As CTM updates arrive through + email, use ctm_rmail to unpack and apply + them. This command can be run directly from an entry in + /etc/aliases in order to automate this + process. Refer to &man.ctm.rmail.1; for more details. Regardless of the method which is used to get deltas, CTM users should subscribe - to the &a.ctm-announce.name; mailing list as - this is the only place where announcements concerning - the operation of the CTM system - are posted. + to the &a.ctm-announce.name; mailing list as this is the + only place where announcements concerning the operation of + the CTM system are posted. <application>CTM</application> Usage - Before CTM - deltas can be used for the first time, a starting point - must be produced. + Before CTM deltas can be used + for the first time, a starting point must be produced. - One method is to apply a starter delta to an - empty directory. A - starter delta can be recognized by - the XEmpty in its name, such as - src-cur.3210XEmpty.gz. - The designation following the X corresponds - to the origin of the initial seed, where - Empty is an empty directory. As a rule, a - base transition from Empty is produced + One method is to apply a starter delta to + an empty directory. A starter delta can be recognized by the + XEmpty in its name, such as + src-cur.3210XEmpty.gz. The designation + following the X corresponds to the origin + of the initial seed, where + Empty is an empty directory. As a rule, + a base transition from Empty is produced every 100 deltas. Be aware that starter deltas are large and - 70 to 80 - Megabytes of gzip'd data is common for the - XEmpty deltas. + 70 to 80 Megabytes of gzip'd data is common + for the XEmpty deltas. - Another method is to copy or extract an initial source from - a - RELEASE media as this can - save a significant transfer of data from the Internet. + Another method is to copy or extract an initial source + from a RELEASE media as this can save a significant transfer + of data from the Internet. - Once a base delta has been created, apply - all deltas with higher numbers. To apply the deltas: + Once a base delta has been created, apply all deltas with + higher numbers. To apply the deltas: &prompt.root; cd /directory/to/store/the/stuff &prompt.root; ctm -v -v /directory/which/stores/the/deltas/src-xxx.* - Multiple deltas can be applied at one time as they - will be processed one at a time and any deltas that are already - applied will be ignored. CTM understands deltas which - have been put through gzip, which saves disk - space. + Multiple deltas can be applied at one time as they will + be processed one at a time and any deltas that are already + applied will be ignored. CTM + understands deltas which have been put through + gzip, which saves disk space. - To - verify a delta without applying it, include . - CTM will not actually touch - the local tree but will instead verify the integrity of the delta - to see if it would apply cleanly. Refer to &man.ctm.1; for - more information about available switches and an overview of - the process CTM uses when applying + To verify a delta without applying it, include + . CTM will not + actually touch the local tree but will instead verify the + integrity of the delta to see if it would apply cleanly. + Refer to &man.ctm.1; for more information about available + switches and an overview of the process + CTM uses when applying deltas. To keep the local source tree up-to-date, every time a - new delta becomes available, apply it through CTM. + new delta becomes available, apply it through + CTM. - Once applied, it is recommended to not delete the deltas if it is a burden to download - them again. This way, a local copy is available in case - something bad happens. + Once applied, it is recommended to not delete the deltas + if it is a burden to download them again. This way, a loca + copy is available in case something bad happens. @@ -315,76 +323,77 @@ a limited way: before checking for the presence of a file, it first looks for a file with the same name and a .ctm extension. If this file exists, - CTM will operate on it instead of the - original filename. + CTM will operate on it instead of + the original filename. This behavior provides a simple way to maintain local - changes. Before modifying a file, make a copy with a - .ctm - suffix. Make any changes to the original filename, knowing that - CTM will only apply updates to the file with the - .ctm suffix. + changes. Before modifying a file, make a copy with a + .ctm suffix. Make any changes to the + original filename, knowing that + CTM will only apply updates to the + file with the .ctm suffix. - Other <application>CTM</application> - Options + Other <application>CTM</application> Options - - Finding Out Exactly What Would Be Touched by an - Update + + Finding Out Exactly What Would Be Touched by an + Update - - To determine the list of changes that - CTM will make to the local source - repository, use . This option is useful for creating logs of the - changes or when performing pre- or post-processing on any of the modified files. - - + + To determine the list of changes that + CTM will make to the local + source repository, use . This option + is useful for creating logs of the changes or when + performing pre- or post-processing on any of the + modified files. + + - - Making Backups Before Updating + + Making Backups Before Updating - - To backup all of the files that - would be changed by a CTM - update, specify . This option - tells CTM to backup all files - touched by the applied - CTM delta to - backup-file. - - + + To backup all of the files that would be changed by + a CTM update, specify + . This option tells + CTM to backup all files + touched by the applied CTM + delta to backup-file. + + - - Restricting the Files Touched by an Update + + Restricting the Files Touched by an Update - - To restrict the - scope of a given CTM update, or - to extract just a few files from a - sequence of deltas, - filtering regular expressions can be specified using - , which specifies which files to process, or , which specifies which files to ignore. + + To restrict the scope of a given + CTM update, or to extract + just a few files from a sequence of deltas, filtering + regular expressions can be specified using + , which specifies which files to + process, or , which specifies which + files to ignore. - For example, to extract an up-to-date copy of - lib/libc/Makefile from a collection - of saved CTM deltas: + For example, to extract an up-to-date copy of + lib/libc/Makefile from a collection + of saved CTM deltas: - &prompt.root; cd /directory/to/extract/to/ + &prompt.root; cd /directory/to/extract/to/ &prompt.root; ctm -e '^lib/libc/Makefile' /directory/which/stores/the/deltas/src-xxx.* - For every file specified in a - CTM delta, - and are - applied in the order given on the command line. A file is - processed by CTM only if it is - marked as eligible after all and - options are applied. - - - + For every file specified in a + CTM delta, + and are + applied in the order given on the command line. A file + is processed by CTM only if + it is marked as eligible after all + and options are applied. + + +