| README.TEMPLATING (92302) | README.TEMPLATING (129101) |
|---|---|
| 1IMPORTANT NOTE: 2 3As of Feb. 11, 2002 (and indeed, for quite some time before that), 4the /etc/rc.diskless{1,2} scripts support a slightly different 5diskless boot process than the one documented in the rest of 6this file (which is 3 years old). 7 8I am not deleting the information below because it contains some 9useful background information on diskless operation, but for the 10actual details you should look at /etc/rc.diskless1, /etc/rc.diskless2, 11and the /usr/share/examples/diskless/clone_root script which can 12be useful to set up clients and server for diskless boot. 13 | 1IMPORTANT NOTE: 2 3As of Feb. 11, 2002 (and indeed, for quite some time before that), 4the /etc/rc.diskless{1,2} scripts support a slightly different 5diskless boot process than the one documented in the rest of 6this file (which is 3 years old). 7 8I am not deleting the information below because it contains some 9useful background information on diskless operation, but for the 10actual details you should look at /etc/rc.diskless1, /etc/rc.diskless2, 11and the /usr/share/examples/diskless/clone_root script which can 12be useful to set up clients and server for diskless boot. 13 |
| 14--- $FreeBSD: head/share/examples/diskless/README.TEMPLATING 92302 2002-03-15 06:47:38Z luigi $ --- | 14--- $FreeBSD: head/share/examples/diskless/README.TEMPLATING 129101 2004-05-10 20:39:32Z simon $ --- |
| 15------------------------------------------------------------------------ 16 17 TEMPLATING machine configurations 18 19 Matthew Dillon 20 dillon@backplane.com 21 22 This document describes a general mechanism by which you can template --- 155 unchanged lines hidden (view full) --- 178 179 By formalizing the delete operation, you can be 100% sure that it is 180 possible to recreate / and /usr on any machine with only the original 181 template and a backup of the ( relatively few ) explicitly-excepted 182 files. The most common mistake a sysop makes is to make a change to a 183 file in / or /usr on a target machine instead of the template machine. 184 If the target machine is updated once a night from cron, the sysop 185 quickly learns not to do this ( because his changes get overwritten | 15------------------------------------------------------------------------ 16 17 TEMPLATING machine configurations 18 19 Matthew Dillon 20 dillon@backplane.com 21 22 This document describes a general mechanism by which you can template --- 155 unchanged lines hidden (view full) --- 178 179 By formalizing the delete operation, you can be 100% sure that it is 180 possible to recreate / and /usr on any machine with only the original 181 template and a backup of the ( relatively few ) explicitly-excepted 182 files. The most common mistake a sysop makes is to make a change to a 183 file in / or /usr on a target machine instead of the template machine. 184 If the target machine is updated once a night from cron, the sysop 185 quickly learns not to do this ( because his changes get overwritten |
| 186 overnight ). With a manual update, these sorts of mistakes can propogate | 186 overnight ). With a manual update, these sorts of mistakes can propagate |
| 187 for weeks or months before they are caught. 188 189 TEMPLATE COPYING AND SAFETY 190 THE CPDUP PROGRAM 191 192 The 'cpdup' program is a program which efficiently duplicates a directory 193 tree. The program copies source to destination, duplicating devices, 194 softlinks, hardlinks, files, modification times, uid, gid, flags, perms, 195 and so forth. The program incorporates several major features: 196 | 187 for weeks or months before they are caught. 188 189 TEMPLATE COPYING AND SAFETY 190 THE CPDUP PROGRAM 191 192 The 'cpdup' program is a program which efficiently duplicates a directory 193 tree. The program copies source to destination, duplicating devices, 194 softlinks, hardlinks, files, modification times, uid, gid, flags, perms, 195 and so forth. The program incorporates several major features: 196 |
| 197 * The program refuses, absolutely, to cross partition boundries. | 197 * The program refuses, absolutely, to cross partition boundaries. |
| 198 i.e. if you were copying the template /usr from an NFS mount to 199 your /usr, and you had a mount point called /usr/home, the 200 template copying program would *NOT* descend into /usr/home on 201 the destination. 202 203 This is a safety. 204 205 * The program accesses a file called .cpignore in each directory | 198 i.e. if you were copying the template /usr from an NFS mount to 199 your /usr, and you had a mount point called /usr/home, the 200 template copying program would *NOT* descend into /usr/home on 201 the destination. 202 203 This is a safety. 204 205 * The program accesses a file called .cpignore in each directory |
| 206 it descending into on the source to obtain a list of exceptions | 206 it descends into on the source to obtain a list of exceptions |
| 207 for that directory -- that is, files not to copy or mess with. 208 209 This is a templating function. 210 211 * The program refuses to delete a directory on the destination 212 being replaced by a softlink or file on the source. 213 214 This is a safety mechanism --- 87 unchanged lines hidden --- | 207 for that directory -- that is, files not to copy or mess with. 208 209 This is a templating function. 210 211 * The program refuses to delete a directory on the destination 212 being replaced by a softlink or file on the source. 213 214 This is a safety mechanism --- 87 unchanged lines hidden --- |