head	1.79;
access;
symbols;
locks
	reed:1.79;
comment	@# @;


1.79
date	2011.05.01.17.05.45;	author bsdwiki;	state Exp;
branches;
next	1.78;

1.78
date	2011.05.01.16.36.41;	author bsdwiki;	state Exp;
branches;
next	1.77;

1.77
date	2011.05.01.16.36.06;	author bsdwiki;	state Exp;
branches;
next	1.76;

1.76
date	2011.05.01.16.35.08;	author bsdwiki;	state Exp;
branches;
next	1.75;

1.75
date	2011.05.01.16.34.16;	author bsdwiki;	state Exp;
branches;
next	1.74;

1.74
date	2011.05.01.16.32.13;	author bsdwiki;	state Exp;
branches;
next	1.73;

1.73
date	2011.05.01.16.21.26;	author bsdwiki;	state Exp;
branches;
next	1.72;

1.72
date	2011.05.01.16.07.49;	author bsdwiki;	state Exp;
branches;
next	1.71;

1.71
date	2011.05.01.16.02.51;	author bsdwiki;	state Exp;
branches;
next	1.70;

1.70
date	2010.08.30.06.46.36;	author bsdwiki;	state Exp;
branches;
next	1.69;

1.69
date	2010.07.23.13.31.22;	author bsdwiki;	state Exp;
branches;
next	1.68;

1.68
date	2010.07.22.15.26.51;	author bsdwiki;	state Exp;
branches;
next	1.67;

1.67
date	2010.07.22.15.24.48;	author bsdwiki;	state Exp;
branches;
next	1.66;

1.66
date	2010.07.22.15.16.34;	author bsdwiki;	state Exp;
branches;
next	1.65;

1.65
date	2010.07.18.15.33.59;	author bsdwiki;	state Exp;
branches;
next	1.64;

1.64
date	2010.07.18.15.32.50;	author bsdwiki;	state Exp;
branches;
next	1.63;

1.63
date	2010.07.18.15.22.09;	author bsdwiki;	state Exp;
branches;
next	1.62;

1.62
date	2010.07.18.15.13.48;	author bsdwiki;	state Exp;
branches;
next	1.61;

1.61
date	2010.07.18.15.05.58;	author bsdwiki;	state Exp;
branches;
next	1.60;

1.60
date	2010.07.18.15.04.59;	author bsdwiki;	state Exp;
branches;
next	1.59;

1.59
date	2010.07.18.14.29.53;	author bsdwiki;	state Exp;
branches;
next	1.58;

1.58
date	2010.07.18.14.29.01;	author bsdwiki;	state Exp;
branches;
next	1.57;

1.57
date	2010.07.11.17.04.57;	author bsdwiki;	state Exp;
branches;
next	1.56;

1.56
date	2010.07.11.17.03.59;	author bsdwiki;	state Exp;
branches;
next	1.55;

1.55
date	2010.07.11.03.51.06;	author bsdwiki;	state Exp;
branches;
next	1.54;

1.54
date	2010.06.30.18.49.52;	author bsdwiki;	state Exp;
branches;
next	1.53;

1.53
date	2010.06.22.16.48.30;	author bsdwiki;	state Exp;
branches;
next	1.52;

1.52
date	2010.06.22.16.38.50;	author bsdwiki;	state Exp;
branches;
next	1.51;

1.51
date	2010.06.22.16.38.00;	author bsdwiki;	state Exp;
branches;
next	1.50;

1.50
date	2010.06.22.16.37.11;	author bsdwiki;	state Exp;
branches;
next	1.49;

1.49
date	2010.06.22.15.32.37;	author bsdwiki;	state Exp;
branches;
next	1.48;

1.48
date	2010.06.22.15.16.40;	author bsdwiki;	state Exp;
branches;
next	1.47;

1.47
date	2010.06.22.14.41.25;	author bsdwiki;	state Exp;
branches;
next	1.46;

1.46
date	2010.06.21.19.36.09;	author bsdwiki;	state Exp;
branches;
next	1.45;

1.45
date	2010.06.21.19.33.28;	author bsdwiki;	state Exp;
branches;
next	1.44;

1.44
date	2010.06.21.19.30.30;	author bsdwiki;	state Exp;
branches;
next	1.43;

1.43
date	2010.06.21.18.57.14;	author bsdwiki;	state Exp;
branches;
next	1.42;

1.42
date	2010.06.21.18.51.21;	author bsdwiki;	state Exp;
branches;
next	1.41;

1.41
date	2010.06.21.18.45.50;	author bsdwiki;	state Exp;
branches;
next	1.40;

1.40
date	2010.06.21.18.36.22;	author bsdwiki;	state Exp;
branches;
next	1.39;

1.39
date	2010.06.20.18.54.28;	author bsdwiki;	state Exp;
branches;
next	1.38;

1.38
date	2010.06.20.18.52.47;	author bsdwiki;	state Exp;
branches;
next	1.37;

1.37
date	2010.06.20.18.38.20;	author bsdwiki;	state Exp;
branches;
next	1.36;

1.36
date	2010.06.20.18.35.55;	author bsdwiki;	state Exp;
branches;
next	1.35;

1.35
date	2010.06.20.18.32.36;	author bsdwiki;	state Exp;
branches;
next	1.34;

1.34
date	2010.06.20.18.31.02;	author bsdwiki;	state Exp;
branches;
next	1.33;

1.33
date	2010.06.20.18.10.51;	author bsdwiki;	state Exp;
branches;
next	1.32;

1.32
date	2010.06.20.18.04.42;	author bsdwiki;	state Exp;
branches;
next	1.31;

1.31
date	2010.06.20.17.44.05;	author bsdwiki;	state Exp;
branches;
next	1.30;

1.30
date	2010.06.20.17.36.16;	author bsdwiki;	state Exp;
branches;
next	1.29;

1.29
date	2010.06.20.17.32.28;	author bsdwiki;	state Exp;
branches;
next	1.28;

1.28
date	2010.06.20.17.31.43;	author bsdwiki;	state Exp;
branches;
next	1.27;

1.27
date	2010.06.20.17.17.58;	author bsdwiki;	state Exp;
branches;
next	1.26;

1.26
date	2010.06.20.16.59.35;	author bsdwiki;	state Exp;
branches;
next	1.25;

1.25
date	2010.06.20.16.52.22;	author bsdwiki;	state Exp;
branches;
next	1.24;

1.24
date	2010.06.15.17.33.00;	author bsdwiki;	state Exp;
branches;
next	1.23;

1.23
date	2010.06.08.15.53.30;	author bsdwiki;	state Exp;
branches;
next	1.22;

1.22
date	2010.06.07.00.17.37;	author bsdwiki;	state Exp;
branches;
next	1.21;

1.21
date	2010.06.07.00.16.43;	author bsdwiki;	state Exp;
branches;
next	1.20;

1.20
date	2010.06.07.00.10.22;	author bsdwiki;	state Exp;
branches;
next	1.19;

1.19
date	2010.06.06.23.19.58;	author bsdwiki;	state Exp;
branches;
next	1.18;

1.18
date	2010.06.06.23.18.34;	author bsdwiki;	state Exp;
branches;
next	1.17;

1.17
date	2010.06.06.23.16.13;	author bsdwiki;	state Exp;
branches;
next	1.16;

1.16
date	2010.06.06.23.14.51;	author bsdwiki;	state Exp;
branches;
next	1.15;

1.15
date	2010.06.06.23.13.09;	author bsdwiki;	state Exp;
branches;
next	1.14;

1.14
date	2010.06.06.20.56.52;	author bsdwiki;	state Exp;
branches;
next	1.13;

1.13
date	2010.06.06.20.55.53;	author bsdwiki;	state Exp;
branches;
next	1.12;

1.12
date	2010.06.06.20.54.21;	author bsdwiki;	state Exp;
branches;
next	1.11;

1.11
date	2010.06.06.20.53.56;	author bsdwiki;	state Exp;
branches;
next	1.10;

1.10
date	2010.06.06.19.15.36;	author bsdwiki;	state Exp;
branches;
next	1.9;

1.9
date	2010.06.06.18.50.13;	author bsdwiki;	state Exp;
branches;
next	1.8;

1.8
date	2010.06.06.17.40.43;	author bsdwiki;	state Exp;
branches;
next	1.7;

1.7
date	2010.06.06.17.39.59;	author bsdwiki;	state Exp;
branches;
next	1.6;

1.6
date	2010.06.06.17.09.47;	author bsdwiki;	state Exp;
branches;
next	1.5;

1.5
date	2010.06.06.17.07.38;	author bsdwiki;	state Exp;
branches;
next	1.4;

1.4
date	2010.06.01.16.31.13;	author bsdwiki;	state Exp;
branches;
next	1.3;

1.3
date	2010.06.01.16.21.40;	author bsdwiki;	state Exp;
branches;
next	1.2;

1.2
date	2010.05.29.19.23.25;	author bsdwiki;	state Exp;
branches;
next	1.1;

1.1
date	2010.05.29.15.53.14;	author bsdwiki;	state Exp;
branches;
next	;


desc
@From ikiwiki
@


1.79
log
@web commit by dru () at 70.26.38.81:
@
text
@## INSTALLATION and SETUP

System installation and setup is a basic but important job of a BSD system administrator. Beyond getting the system up and running, the BSDP candidate must be able to perform more complex tasks such as preparing and updating automated installation scripts, using a serial console for installation, restoring a corrupted boot sector, and other similar tasks.

--------------------


###  3.1.1. Build and install system from source code.

Importance: 3.6, Frequency: 1.7, Bloom: K,C

**Concept:** BSD systems allow the administrator to compile both the kernel and userland from source in order to upgrade an existing operating system. The commands provided for this purpose vary between the BSDs.

BSDP candidates should be familiar with the steps required to compile both kernel and userland from source and to install the new kernel and userland for their BSD of choice.

**Practical:**

Dragonfly BSD: build(7), development(7), make(1)

FreeBSD: config(8), make(1), mergemaster(8)

NetBSD: build.sh, etcupdate(8), postinstall(8)

OpenBSD: config(8), make(1), sysmerge(8)

**Estimated Time:** 

10 minutes to describe the steps required to build and install a system from source code.

###  3.1.2. Use disklabel to modify or create partitions.

Importance: 3.5, Frequency: 1.4, Bloom: K,C,A

**Concept:**

*Note:* bsdlabel was removed from objective as disklabel is available on all BSDs.

The disklabel utility can be used to install, examine, or modify the label on a hard drive. The disk label contains information about the size and type of disk and the partition layout. While each BSD provides the disklabel utility, the command
parameters and usage of the utility vary by BSD.

BSDP candidates should be able to view, modify, or create the disk label on a BSD system.

**Practical:**

disklabel(8)

**Estimated Time:** 

10 minutes to create or modify an existing disk label according to a specification. 

###  3.1.3. Use fdisk tool.

Importance: 3.3, Frequency: 1.5, Bloom: K,C,A

**Concept:** Note this objective was renamed. The phrase "modify or create partitions" was removed.

On BSD systems, the built-in fdisk utility is either used to view and modify the disk slice table or to view and modify the master boot record.

BSDP candidates should be able to either modify the disk slice table or the master boot record using the built-in fdisk utility, depending upon their BSD of choice.

**Practical:**

fdisk(8)

**Estimated Time:** 

10 minutes to create or edit the disk slice table or master boot record according to a specification.


<font color="#A0A0A0">

###  Change Partition IDs to other BSD or non-BSD IDs.

Importance: 2.5, Frequency: 1.2, Bloom:

**Concept:** DRU: Should we keep this objective which falls below both cutoff threshholds? If so, do we want them to do this during the install or go back into the installer utility afterwards? Or does the next objective make more sense to test than this one?

@@@@@@jpb: recommend dropping this one, and keeping the Objective 5


**Practical:**

**Estimated Time:**

</font>

###  3.1.4. Create FAT32, NTFS, or other non-BSD partitions.

Importance: 2.5,  Frequency: 1.3, Bloom: K,C,A

**Concept:**

Creating a non-BSD disk partition is the first step in creating a filesystem
used by other operating systems.  The partition is assigned an
identifier that marks it as a non-BSD partition.  

BSDP candidates should be familiar with all the steps in the creation of a filesystem and be able to configure a disk partition as the first step
in preparing a non-BSD filesystem.

**Practical:**

fdisk(8), disklabel(8)

**Estimated Time:**

10 minutes to create a non-BSD partition according to a specification.

<font color="#A0A0A0">
###  Create or edit the device.hints or loader.conf file.

Importance: 3.2, Frequency: 1.4, Bloom: 

**Concept:** *BSDCG Note: This objective was removed at the 15/5/10 SME session.*

**Practical:**

**Estimated Time:**</font>

<font color="#A0A0A0">

###  Perform a 'headless' install using serial console.

Importance: 2.8, Frequency: 1.4, Bloom: 

**Concept:** *BSDCG Note: This objective was removed at the 15/05/10 SME session.*

**Practical:**

**Estimated Time:**
</font>

###  3.1.5. Create an install script or configuration for unattended installation.

Importance: 3.2, Frequency: 1.4, Bloom: K,C,A

**Concept:**

Creating a script for unattended installation relieves the BSD system administrator of manually repeating the same task  when installing multiple systems.
BSDP candidates should be able to configure a script for unattended installation or post-installation configuration of a BSD system.

**Practical:**

software of choice in packages/pkgsrc

FreeBSD: sysinstall(8)

OpenBSD: install.site or upgrade.site

**Estimated Time:**

20 minutes to create, install, and test an install script according to a specification.

<font color="#A0A0A0">
###  Create an ISO installation image.

Importance: 2.8, Frequency: 1.4, Bloom: 

**Concept:** *BSDCG Note: This objective was removed at the 15/5/10 SME session. It should be considered for a Global Enterprise exam.*

**Practical:**

**Estimated Time:**
</font>

<font color="#A0A0A0">
### Create an emergency repair disk.

Importance: 3.1, Frequency: 1.3, Bloom: 

**Concept:** *BSDCG Note: This objective was removed at the 15/5/10 SME session.*

**Practical:**

**Estimated Time:**
</font>

### 3.1.6. Configure startup scripts to be run at boot time.

Importance: 3.3, Frequency: 1.9, Bloom: K,C,A

**Concept:**

Note: This objective was modified during the July 18, 2010 SME session.

BSD systems perform startup operations by means of scripts that are run at boot time.

BSDP candidates should be able to enable and disable system, third-party, and custom services at boot time, as well as temporarily start a service without configuring it to start at boot time.

**Practical:**

rc(8), rc.conf(5)

**Estimated Time:**

5 minutes to enable or disable a service to start at boot time.

<font color="#A0A0A0">
### Install a boot manager.

Importance: 3.3, Frequency: 1.5, Bloom: 

**Concept:** *BSDCG Note: This objective was removed at the 15/5/10 SME session. It should be considered for a Desktop or an Embedded exam.*

**Practical:**

**Estimated Time:**
</font>

### 3.1.7. Restore a corrupted boot sector.

Importance: 3.6, Frequency: 1.3, Bloom: K,C,A

**Concept:**

A corrupted boot sector prevents the system from booting normally.  Restoring the
boot sector can enable the system to boot, or enable the administrator to
access files on the affected disk.

BSDP candidates should be able to restore the master boot record of a disk.

**Practical:**

software of choice for packages/pkgsrc

fdisk(8)

NetBSD, OpenBSD: scanffs(8)

**Estimated Time:**

10 minutes to restore a corrupted boot sector.

### 3.1.8. Boot via the serial console.

Importance: 2.9, Frequency: 1.6, Bloom: K

**Concept:**

Using a serial device for booting the system permits the system to be booted when there is no attached keyboard and/or display device.

BSDP candidates should know how to configure a BSD system to use an attached serial device
during the boot loader and kernel load, all the way to a login prompt. 

**Practical:**

ttys(5)

FreeBSD: loader.conf(5)

OpenBSD: boot(8)

**Estimated Time:**

20 minutes to configure and test booting the system from a serial console.

<font color="#A0A0A0">
### Configure a splash screen at boot.

Importance: 1.6, Frequency: 1.1, Bloom: 

**Concept:** *BSDCG Note: This objective was removed at the 15/5/10 SME session.*

**Practical:**

**Estimated Time:**
</font>

### 3.1.9. Configure sysctl values to be loaded at system startup.

Importance: 4.0, Frequency: 1.9, Bloom: K,C, A

**Concept:**

Note: This objective was reworded during the July 18, 2010 SME session.

**Concept:**

BSD systems utilize an internal "Management Information Base" (MIB) that contains a collection of variables and values
that maintain kernel state.  The values of some of these variables can be changed by the system administrator.

BSDP candidates should understand the use of the MIB to maintain kernel state, be able to configure custom
MIB values on a live system, and configure the system to preserve custom values after a system boot.

**Practical:**

sysctl(7) or (8), sysctl.conf(5)

**Estimated Time:**

10 minutes to set custom MIB values and configure the system to preserve the values after a system boot, according to a specification.

<font color="#A0A0A0">
###  Password protect single user mode.

Importance: 3.5, Frequency: 1.4, Bloom: 

**Concept:** *BSDCG Note: This objective was removed at the 15/5/10 SME session.*

**Practical:**

**Estimated Time:**
</font>

### 3.1.10. Configure BSD system for PXE booting.

Importance: 3.1, Frequency: 1.6, Bloom: K,C,A

**Concept:**

NOTE: This objective requires multiple steps and is best suited to a lab exercise. 

Preboot Execution Environment (PXE) allows diskless systems to access a network's resources using a network interface.

BSDP candidates should understand the PXE boot process and be able to configure a BSD PXE boot server to enable diskless systems to boot and access network resources.  Candidates should also be able to configure the services necessary for a PXE boot environment: i) DHCP or bootp server; and ii) TFTP or NFS.

**Practical:**

software of choice from packages/pkgsrc

pxeboot(8), diskless(8)

**Estimated Time:**

30 minutes to configure a BSD PXE boot server and test a diskless workstation according to a specification.

### 3.1.11. Configure system to mount remote network filesystems at boot.

Importance: 3.7, Frequency: 2.2, Bloom: K,C,A

**Concept:**

BSD systems can be configured to access remote Network File System (NFS) shares over a network at boot time.

BSDP candidates should be able to configure a BSD system to access NFS shares over a network.

**Practical:**

fstab(5)

DragonFly BSD, FreeBSD: rc.conf(5)

**Estimated Time:**

15 minutes to configure a BSD system to mount remote NFS shares at boot time according to a specification.

<font color="#A0A0A0">
### Create and install a jail.  

(@@@@@@jpb: MOVED to VIRTUALIZATION section)

### Prepare a host system for jails.

@@@@@@jpb: Note: This objective was integrated into objective 174 and removed from this section during the July 18, 2010 SME session.

### Start or shutdown a jail.

@@@@@@jpb: this objective was moved to the VIRTUALIZATION section during the July 18, 2010 SME Session.
</font>

### 3.1.12. Create a local package repository.

Importance: 3.3, Frequency: 1.7, Bloom: K,C,A

**Concept:** 

While each BSD project provides its own official package repository, it is often desirable for a system administrator to create a local repository containing only those packages needed by the organization.

BSDP candidates should be able to configure a local repository containing a subset of the packages collection or pkgsrc.  In addition, BSDP candidates should be aware of the environment variables and program switches needed to modify the default path used when installing packages.

**Practical:**

pkg_add(1)

**Estimated Time:**

20 minutes to configure and test a local package repository according to a specification.

### 3.1.13. Compile a customized binary using ports or pkgsrc.

Importance: 4.2, Frequency 3.0, Bloom: K,C,A

**Concept:** Objective renamed. The phrase ",packages" was removed.

System administrators often need to install customized software compiled from source code.

BSDP candidates should be able to compile a customized binary using either the ports collection or pkgsrc. This may require the use of make(1) targets, customizing a port's Makefile, or setting pkgsrc environmental variables.

**Practical:**

The pkgsrc Guide

make(1)

FreeBSD, OpenBSD: ports(7) 

**Estimated Time:**

10 minutes to compile and test customized software according to a specification.

<font color="#A0A0A0">
### Compress a kernel.

Importance: 2.5, Frequency: 1.4, Bloom:

**Concept:** *BSDCG Note: This objective was removed at the 15/5/10 SME session. It should be considered for an Embedded exam.*

**Practical:**

**Estimated Time:**
</font>

<font color="#A0A0A0">
###  Perform cross-platform building, such as using build.sh or 'make universe'

Importance: 2.4, Frequency: 1.2, Bloom: 

**Concept:** *BSDCG Note: This objective was removed at the 15/5/10 SME session. It should be considered for an Embedded exam.*

**Practical:**

**Estimated Time:**
</font>
@


1.78
log
@web commit by dru () at 70.26.38.81:
@
text
@d3 1
a3 4
Installation and setup is a basic, but important job of a BSD  system administrator.
Beyond getting the system up and running, the BSDP candidate must be able to perform
more complex tasks such as preparing and updating automated installation scripts, using a
serial console for installation, restoring a corrupted boot sector, and other similar tasks.
@


1.77
log
@web commit by dru () at 70.26.38.81:
@
text
@d404 1
a404 1
### 25. Compress a kernel.
@


1.76
log
@web commit by dru () at 70.26.38.81:
@
text
@d350 1
a350 1
### 20. Create and install a jail.  
d354 1
a354 2
<font color="#A0A0A0">
### 21. Prepare a host system for jails.
d358 1
a358 1
### 22. Start or shutdown a jail.
@


1.75
log
@web commit by dru () at 70.26.38.81:
@
text
@a358 1
<font color="#A0A0A0">
@


1.74
log
@web commit by dru () at 70.26.38.81:
@
text
@a362 1

@


1.73
log
@web commit by dru () at 70.26.38.81:
@
text
@d271 1
a271 1
### 16. Configure sysctl values to be loaded at system startup.
a276 2
DRU: as worded, this objective is vague (e.g. kernel modules is clearer than custom kernel tunables) and does not support all BSDs as NetBSD and OpenBSD do not provide a loader.conf to configure automatic loading. It should be reworded to specify either (or both) of i. load a kernel module at boot time, ii) load/unload a kernel module at runtime.  It is also less common to load runtime modules on NetBSD and OpenBSD systems.

d279 1
a279 3
@@@@@@jpb: The objective was reworded to apply to sysctl
values instead of kernel modules.  The vagueness has been removed.

d282 1
a282 1
that maintain kernel state.  The values of these variables can be changed by the system administrator.
a285 1
 
d289 1
a289 1
sysctl(7), sysctl(8), sysctl.conf(5)
a294 1

d296 1
a296 1
### 17. Password protect single user mode.
d307 1
a307 1
### 18. Configure BSD system for PXE booting.
d313 1
a313 1
Preboot Execution Environment (PXE) allows diskless systems to bootstrap themselves through network access to system resources.
d315 1
a315 4
BSDP candidates should understand the PXE boot process and be able to configure
a BSD PXE boot server to enable a diskless system to boot and access network resources.

@@@@@@jpb: This objective requires multiple steps and is best suited to a lab exercise. 
d317 1
d321 1
a321 3
BSDA candidates should be able to setup the services necessary for a PXE boot environment.

It requires: i) configuring DHCP or bootp server; and  ii) configuring TFTP or NFS.
d327 1
a327 1
30 minutes to configure a BSD PXE boot server and boot a diskless workstation according to a specification.
d329 1
a329 2

### 19. Configure system to mount remote network filesystems at boot.
d335 3
a337 1
BSDP candidates should be able to configure a BSD filesystem to be available over a network, according to a set of specifications which may indicate the directories to be shared, the permissions available to remote users, and which users/networks have access to the data.
d341 1
a341 1
nfsd(8), mountd(8), amd(8), exports(5)
d343 1
a343 1
rpcbind(8) or portmap(8)
d347 1
a347 3
15 minutes to configure a BSD system to mount remote filesystems at boot time according to a specification.


d350 1
a350 23
### 20. Create and install a jail.  (@@@@@@jpb: MOVED to VIRTUALIZATION section)

Importance: 3.8, Frequency: 2.2, Bloom: K,C,

**Concept:** XXX-HF This is 1) specific to a subset of *BSD, and 2) better belongs to the VIRTUALIZATION section. DRU: since specific to FreeBSD, requires alternate questions and/or lab scenario with equal weighting.

Jails can be created to sandbox a single executable, or to provide a complete
virtual system for use by many services and programs. Both cases require
almost all system files from a typical FreeBSD or DragonFly BSD installation.

BSDP candidates should be able to perform the necessary steps to create a jail and
populate the jail directory tree. For creating a virtual system image,
there are additional steps required to make the jail usable.  Configuration
of accounts and passwords, filesystems, name resolution, and other details
are necessary.   Some configuration steps take place in the host environment,
others take place inside the running jail environment and BSDP candidates
should be able to configure relevant details on both environments.

**Practical:**

jail(8), jexec(8), sysctl.conf(5), sysctl(8), devfs(8), mount(8), umount(8)

**Estimated Time:**
d352 1
a352 2
25 minutes to configure a jail for installation
</font>
d355 1
a355 10
### 21. Prepare a host system for jails.(@@@@@@jpb: MOVED to VIRTUALIZATION section)


Importance: 3.8, Frequency: 2.0, Bloom: K,C,A

**Concept:**

XXX-HF This is 1) specific to a subset of *BSD, and 2) better belongs to the VIRTUALIZATION section.

DRU: since specific to FreeBSD, requires alternate questions and/or lab scenario with equal weighting.
a358 29

BSD systems that utilize jails often configure certain operations on the host that restrict
certain activities within jails.  For example, by configuring the security.jail.param.children.max
the host system administrator can restrict the number of jails and jail descendants that can
be started on the host; and security.jail.allow.set_hostname which permits the jail administrator
to set the hostname of the jail from within the jail.

Other necessary tasks are:

* Setting up a Jail Directory Tree
* Adjust IP services on the host to be 'jail friendly'.  This may mean
configuring services to listen on specific IP addresses only (instead
of listening on all local addresses for a service).  This may also mean
recompiling services to operate correctly in a jail hosting environment.
* Configuring each jail that will be used
* Configuring the host startup scripts to start jails at boot time.

Jails are a feature on FreeBSD and DragonFly BSD systems.

**Practical:**

jail(8), jexec(8), sysctl(8), sysctl.conf(5), rc(8), rc.conf(5), devfs(8),
inetd(8) 

**Estimated Time:**

10 minutes to prepare a system for jails according to a specification.
</font>

d360 1
a360 10
### 22. Start or shutdown a jail.(@@@@@@jpb: MOVED to VIRTUALIZATION section)


Importance: 3.8, Frequency: 2.5, Bloom: K

**Concept:**

XXX-HF This is 1) specific to a subset of *BSD, and 2) better belongs to the VIRTUALIZATION section.

DRU: since specific to FreeBSD, requires alternate question with equal weighting.
a363 17


Jails on FreeBSD or DragonFly BSD are actually just programs that exist on the host
that utilize a specially prepared file which contains a 'virtual system image' for the
root of the jail.  Preparing the system image is the topic of the previous
objective "Prepare a host system for jails."

To start or shutdown a jail, the host administrator uses jail(8) with appropriate options.
Note that it may be necessary to configure the virtual interface the jail will use,
and mount a proc filesystem for jail use.

**Practical:**

jail(8)

**Estimated Time:**

d366 1
a366 1
### 23. Create an internal package repository.
d370 1
a370 1
**Concept:** This could part of a lab scenario that builds on objective 1.19.
d372 3
a374 1
BSDP candidates should be aware of the environment variables required to change the default path used when installing packages. In addition, BSDP candidates should be able to configure a custom repository containing only the packages required in an internal environment using either the packages collection or pkgsrc.
d382 1
a382 1
5 minutes (not counting time to configure sharing of directory containing the packages)
d384 1
a384 1
### 24. Compile a customized binary using ports or pkgsrc.
d390 3
a392 1
BSDP candidates should be able to compile a customized binary given a set of specifications using either the ports collection or pkgsrc. This may require the use of make(1) targets, customizing a port's Makefile, or setting pkgsrc environmental variables.
d396 3
a398 1
ports(7) (not available on NetBSD)
d400 1
a400 1
The pkgsrc Guide
d404 1
a404 1
5 minutes (assuming only configuration is tested without waiting for compile to complete)
d419 1
a419 1
### 26. Perform cross-platform building, such as using build.sh or 'make universe'
a428 2


@


1.72
log
@web commit by dru () at 70.26.38.81:
@
text
@d97 2
a98 8
typically used by other operating systems.  The partition is assigned a well known
identifier that marks it as a non-BSD partition.  Creating the filesystem itself
can be done with native BSD tools, or by moving the disk to another system and using tools on
that system to create the filesystem. 

BSDP candidates should be familiar with all steps in the creation of a filesystem
(BSD or non-BSD) and be able to configure a disk partition as the first step
in creating the filesystem.
d100 2
a101 3
DRU: Should we keep this objective which falls below both cutoff threshholds? Does it make more sense to use the tools that come with other operating systems to make non-BSD partitions?

@@@@@@jpb: content added
a106 1

a110 1

d112 1
a112 1
###  6. Create or edit the device.hints or loader.conf file.
d124 1
a124 1
###  7. Perform a 'headless' install using serial console.
d135 1
a135 1
###  8. Create install script or configuration for unattended installation.
d139 4
a142 1
**Concept:** DRU: this objective needs to be checked that it is doable on all BSDs  @@@@@@jpb: check
d146 1
a146 3
FreeBSD: sysinstall(8), /usr/src/usr.sbin/sysinstall/install.cfg

NetBSD: misc/py-anita
d148 1
a148 1
OpenBSD: install.site or upgrade.site 
d150 1
a150 1
DragonFly BSD: roll your own?
d154 1
a154 1
20 minutes (assuming tools exist) to create, install, and test an install script according to a specification.
d157 1
a157 1
###  9. Create an ISO installation image.
d169 1
a169 1
### 10. Create an emergency repair disk.
d180 1
a180 1
### 11. Configure startup scripts to be run at boot time.
a185 2
DRU: is it the order that is important or knowing what services will be started at boot time?

d188 1
d201 1
a201 1
### 12. Install a boot manager.
d212 1
a212 1
### 13. Restore a corrupted boot sector.
d226 5
a230 1
fdisk(8), scanffs(8)
d236 1
a236 1
### 14. Boot via the serial console.
d242 1
a242 3
Using a serial device for booting the system enables the boot messages, normally directed
to the console display, to be output instead to the serial device.  This permits the system
to be booted when there is no attached keyboard and/or display device.
d247 3
a249 1
BSDP candidates should also know how to edit /etc/ttys in order to access the system through a serial console.
d251 1
a251 1
**Practical:**
d253 1
a253 1
loader.conf(5), boot.cfg(5), sio(4), boot(8), ttys(5)
d260 1
a260 1
### 15. Configure a splash screen at boot.
@


1.71
log
@web commit by dru () at 70.26.38.81:
@
text
@d11 1
a11 1
###  1. Build and install system from source code.
d33 1
a33 1
###  2. Use disklabel to modify or create partitions.
d44 1
a44 1
BSDP candidates should be able to view and modify the existing disk label on a BSD system.
d54 1
a54 1
###  3. Use fdisk tool.
d60 1
a60 1
On BSD systems, the built-in fdisk utility is either used to view and modify the disk slice table (FreeBSD and DragonFly BSD) or to view and modify the master boot record (NetBSD and OpenBSD).
d70 1
a70 1
10 minutes to create or edit the disk slice table according to a specification.
d75 1
a75 1
###  4. Change Partition IDs to other BSD or non-BSD IDs.
d90 1
a90 1
###  5. Create FAT32, NTFS, or other non-BSD partitions.
@


1.70
log
@web commit by farrokhi () at 92.48.119.83: pkg_add belongs to section 1 instead of 8
@
text
@d13 1
a13 1
Importance: 3.6, Frequency: 1.7, Bloom: K,C,A
d17 1
a17 1
BSDP candidates should be familiar with the steps required to obtain system source, compile both kernel and userland, and install the new kernel and userland for their BSD of choice.
d21 3
a23 1
FreeBSD: csup(1), make(1), mergemaster(8)
d27 1
a27 3
OpenBSD: cvs(1), make(1), config(8)

Dragonfly BSD: git(1), make(1)
d31 1
a31 1
Varies by hardware, but completion of task will be too long for a lab exam. Candidates may be asked to automate the required steps.
@


1.69
log
@web commit by jpb () at 64.101.230.132: reworded #16 (removed 'according to a specification')
@
text
@d479 1
a479 1
pkg_add(8)
@


1.68
log
@web commit by jpb () at 64.101.230.132: minor edits
@
text
@d276 1
a276 1
### 16. Configure sysctl values to be loaded at system startup time according to a specification.
@


1.67
log
@web commit by jpb () at 64.101.230.132: content updates and minor edits
@
text
@d3 1
a3 1
Installation and setup is a basic, but important job of a BSD Professional system administrator.
d77 1
a77 1
Importance: 2.5, Frequency: 1.2, Bloom: @@@@@@
d506 1
a506 1
Importance: 2.5, Frequency: 1.4, Bloom: @@@@@@
d518 1
a518 1
Importance: 2.4, Frequency: 1.2, Bloom: @@@@@@
@


1.66
log
@web commit by jpb () at 64.101.230.132: content updates and minor edits
@
text
@a362 1
### 20. Create and install a jail.
d364 5
a368 1
Importance: 3.8, Frequency: 2.2, Bloom: K,C,A
d391 1
d393 2
a395 2
<font color="#A0A0A0">
### 21. Prepare a host system for jails.
d437 2
a438 1
### 22. Start or shutdown a jail.
d489 1
a489 1
**Concept:** Objective renamed to remove ",packages".
@


1.65
log
@web commit by jpb () at 98.180.198.168: minor edits
@
text
@d31 1
a31 1
Varies by hardware, but completion of task will be too long for a lab scenario. Candidates may be asked to automate the required steps.
d41 2
a42 1
The disklabel utility can be used to install, examine, or modify the label on a hard drive. The disk label contains information about the size and type of disk and the partition layout. While each BSD provides the disklabel utility, the switches and usage of the utility vary by BSD.
d44 1
a44 1
BSDP candidates should be able to view and modify the existing disk label on their BSD of choice, as well as create a new partition using this utility.
d52 1
a52 1
10 minutes
d58 1
a58 1
**Concept:** Note this objective was renamed to remove "modify or create partitions".
d70 1
a70 1
10 minutes
d81 1
a81 1
@@@@@@jpb: recommend dropping this one, and keeping the next one
d92 1
a92 1
Importance: 2.5,  Frequency: 1.3, Bloom: @@@@@@
d99 2
a100 2
can be done with native BSD tools, or by moving the disk and using tools on
another system to create the filesystem. 
d123 1
a123 1
Importance: 3.2, Frequency: 1.4, Bloom: @@@@@@
d135 1
a135 1
Importance: 2.8, Frequency: 1.4, Bloom: @@@@@@
d148 1
a148 1
**Concept:** DRU: this objective needs to be checked that it is doable on all BSDs
d160 3
a162 1
**Estimated Time:** 20 minutes, assuming tools exist
d167 1
a167 1
Importance: 2.8, Frequency: 1.4, Bloom: @@@@@@
d179 1
a179 1
Importance: 3.1, Frequency: 1.3, Bloom: @@@@@@
d190 1
a190 1
Importance: 3.3, Frequency: 1.9, Bloom: K
d207 1
a207 1
5 minutes
d212 1
a212 1
Importance: 3.3, Frequency: 1.5, Bloom: @@@@@@
d228 3
a230 1
boot sector can 
d239 1
a239 1
10 minutes
d262 1
a262 1
20 minutes to configure and test booting the system from a serial console
d267 1
a267 1
Importance: 1.6, Frequency: 1.1, Bloom: @@@@@@
d271 1
a271 1
**Practical:**co
d289 1
d309 1
a309 1
Importance: 3.5, Frequency: 1.4, Bloom: @@@@@@
d324 1
a324 1
"Preboot Execution Environment" (PXE) allows diskless systems to bootstrap themselves through network access to system resources.
d334 1
a334 2
BSDA candidates should be able to setup the services necessary for a PXE boot environment. 
It requires: i) configuring DHCP or bootp server; and configuring ii) TFTP or NFS.
d336 1
d361 1
a361 1
15 minutes
@


1.64
log
@web commit by jpb () at 98.180.198.168: Note: This objective was modified during the July 18, 2010 SME session.
@
text
@d324 2
d329 1
a329 1
It requires: i) configuring DHCP or bootp server; and configuring ii) TFTP or NFS
@


1.63
log
@web commit by jpb () at 98.180.198.168: Note: This objective (22) was moved to the virtualization section during the July 18, 2010 SME session.
@
text
@d316 6
a321 1
**Concept:** This objective requires multiple steps and is best suited to a lab exercise. It requires: i) configuring DHCP or bootp server; and configuring ii) TFTP or NFS
d323 1
d326 3
a328 1
BSDA candidates should be able to setup the services necessary for a PXE boot environment.
d334 2
a335 1
30 minutes
@


1.62
log
@web commit by jpb () at 98.180.198.168: Note: This objective was modified during the July 18, 2010 SME session.
@
text
@d415 1
d420 9
a428 1
**Concept:** XXX-HF This is 1) specific to a subset of *BSD, and 2) better belongs to the VIRTUALIZATION section. DRU: since specific to FreeBSD, requires alternate question with equal weighting.
d445 2
@


1.61
log
@web commit by jpb () at 98.180.198.168: removed grey
@
text
@d372 2
d378 8
a385 1
**Concept:** XXX-HF This is 1) specific to a subset of *BSD, and 2) better belongs to the VIRTUALIZATION section. DRU: since specific to FreeBSD, requires alternate questions and/or lab scenario with equal weighting.
d412 2
a413 1
10 minutes
@


1.60
log
@web commit by jpb () at 98.180.198.168: Note: This objective was modified during the July 18, 2010 SME session.
@
text
@d270 1
a270 1
<font color="#A0A0A0">
a299 2
</font>

@


1.59
log
@web commit by jpb () at 98.180.198.168: formatting
@
text
@d266 1
a266 1
**Practical:**
d270 8
d279 1
a279 1
### 16. Configure custom kernel tunables to be enabled at boot time.
d281 5
a285 1
Importance: 4.0, Frequency: 1.9, Bloom: K,C, A
d287 3
a289 1
**Concept:** DRU: as worded, this objective is vague (e.g. kernel modules is clearer than custom kernel tunables) and does not support all BSDs as NetBSD and OpenBSD do not provide a loader.conf to configure automatic loading. It should be reworded to specify either (or both) of i. load a kernel module at boot time, ii) load/unload a kernel module at runtime.  It is also less common to load runtime modules on NetBSD and OpenBSD systems.
d293 2
d297 5
@


1.58
log
@web commit by jpb () at 98.180.198.168: Note: This objective was modified during the July 18, 2010 SME session.
@
text
@d192 1
@


1.57
log
@web commit by jpb () at 98.180.198.168: minor edits
@
text
@d185 1
a185 1
### 11. Display the order of startup steps/scripts to be run at boot time.
d189 5
a193 1
**Concept:** DRU: is it the order that is important or knowing what services will be started at boot time?
@


1.56
log
@web commit by jpb () at 98.180.198.168: formatting
@
text
@d6 1
a6 1
serial console for installation, restoring a corrupted boot sector, and other such tasks.
@


1.55
log
@web commit by jpb () at 98.180.198.168: content update
@
text
@d37 3
a39 1
**Concept:** Note: bsdlabel was removed from objective as disklabel is available on all BSDs.
@


1.54
log
@web commit by jpb () at 64.101.230.132:
@
text
@d69 3
d78 3
d85 2
d91 15
a105 1
**Concept:** DRU: Should we keep this objective which falls below both cutoff threshholds? Does it make more sense to use the tools that come with other operating systems to make non-BSD partitions?
d109 3
d114 3
d223 1
a223 1
fdisk(8)
d235 8
a242 1
BSDP candidates should know how to edit /etc/ttys in order to access the system through a serial console.
d246 1
a246 1
ttys(5)
d250 1
a250 1
5 minutes
@


1.53
log
@web commit by dru () at 67.70.104.84:
@
text
@d189 2
@


1.52
log
@web commit by dru () at 67.70.104.84:
@
text
@d379 1
a379 1
### 24. Compile a customized binary using ports, packages, or pkgsrc.
d381 1
a381 1
Importance: 4.2, Frequency 3.0, Bloom: @@@@@@
d383 3
a385 1
**Concept:**
d389 4
d395 2
@


1.51
log
@web commit by dru () at 67.70.104.84:
@
text
@d369 2
a372 2
BSDP candidates should be aware of the environment variables required to change the default path used when installing packages. In addition, BSDP candidates should be able to configure a custom repository containing only the packages required in an internal environment using either the packages collection or pkgsrc.

@


1.50
log
@web commit by dru () at 67.70.104.84:
@
text
@d346 1
a346 3
**Concept:**

XXX-HF This is 1) specific to a subset of *BSD, and 2) better belongs to the VIRTUALIZATION section. DRU: since specific to FreeBSD, requires alternate question with equal weighting.
@


1.49
log
@web commit by dru () at 67.70.104.84:
@
text
@d344 1
a344 1
Importance: 3.8, Frequency: 2.5, Bloom: @@@@@@
d348 1
a348 1
XXX-HF This is 1) specific to a subset of *BSD, and 2) better belongs to the VIRTUALIZATION section 
d361 1
a361 2
jail(8), 

d367 1
a367 1
Importance: 3.3, Frequency: 1.7, Bloom: @@@@@@
d369 1
a369 1
**Concept:**
d373 4
d379 2
@


1.48
log
@web commit by dru () at 67.70.104.84:
@
text
@d271 2
d281 2
d285 1
a285 1
Importance: 3.8, Frequency: 2.2, Bloom: @@@@@@
d287 1
a287 3
**Concept:**

XXX-HF This is 1) specific to a subset of *BSD, and 2) better belongs to the VIRTUALIZATION section 
a304 1

a308 1

d311 1
a311 1
Importance: 3.8, Frequency: 2.0, Bloom: @@@@@@
d313 1
a313 3
**Concept:**

XXX-HF This is 1) specific to a subset of *BSD, and 2) better belongs to the VIRTUALIZATION section 
@


1.47
log
@web commit by dru () at 67.70.104.84:
@
text
@d253 1
a253 1
**Concept:** This objective requires multiple steps and is best suited to a lab exercise: i) configuring DHCP or bootp server; ii) TFTP or NFS
d257 2
d267 1
a267 1
Importance: 3.7, Frequency: 2.2, Bloom: @@@@@@
d273 4
@


1.46
log
@web commit by dru () at 67.70.104.84:
@
text
@d251 1
a251 1
Importance: 3.1, Frequency: 1.6, Bloom: @@@@@@
d253 1
a253 1
**Concept:**
d257 2
d261 2
@


1.45
log
@web commit by dru () at 67.70.104.84:
@
text
@d125 1
a125 1
OpenBSD: roll your own?
@


1.44
log
@web commit by dru () at 67.70.104.84:
@
text
@d231 1
a231 1
**Concept:** DRU: as worded, this objective is vague (e.g. kernel modules is clearer than custom kernel tunables) and does not support all BSDs. It should be reworded to specify either (or both) of i. load a kernel module at boot time, ii) load/unload a kernel module at runtime. NetBSD and OpenBSD do not provide a loader.conf to configure automatic loading. It is also less common to load runtime modules on NetBSD and OpenBSD systems.
a234 2
BSDP candidates 

a235 3
o
loader(8), loader.conf(5), kldload(8) on FreeBSD and DragonFly BSD
modload(8) on NetBSD and OpenBSD
d239 1
d250 1
a252 1

d260 1
a262 1

d270 1
d300 1
d334 1
a335 1
### 22. Start or shutdown a jail.
a350 1

d358 1
a359 1
### 23. Create an internal package repository.
d369 1
a371 1

d380 1
a382 1

d392 1
a394 1

@


1.43
log
@web commit by dru () at 67.70.104.84:
@
text
@d229 1
a229 1
Importance: 4.0, Frequency: 1.9, Bloom: @@@@@@
d231 1
a231 1
**Concept:**
d235 2
d238 3
@


1.42
log
@web commit by dru () at 67.70.104.84:
@
text
@d201 1
a201 1
Importance: @@@@@@I, Frequency: @@@@@@F, Bloom: @@@@@@
d203 1
d205 1
a205 1
**Concept:**
d209 2
d213 2
d218 1
a218 1
Importance: @@@@@@I, Frequency: @@@@@@F, Bloom: @@@@@@
d228 1
@


1.41
log
@web commit by dru () at 67.70.104.84:
@
text
@d185 1
a185 1
Importance: 3.6, Frequency: 1.3, Bloom: @@@@@@
d189 2
d193 2
d197 2
@


1.40
log
@web commit by dru () at 67.70.104.84:
@
text
@d12 1
d34 1
d70 1
d80 1
d91 1
d103 1
d114 1
d133 1
a135 1

d145 1
a147 1

a155 1
Importance: 3.3, Frequency: 1.9, Bloom: @@@@@@
d157 1
d159 3
a161 1
**Concept:**
d165 2
d169 2
d173 1
a175 1

d184 1
a186 1

d194 1
d206 1
a208 1

@


1.39
log
@web commit by dru () at 67.70.104.84:
@
text
@d110 1
a110 3
**Concept:** 


d120 1
a120 1
DragonFly BSD:
d122 1
a122 1
**Estimated Time:** 20 minutes
@


1.38
log
@web commit by dru () at 67.70.104.84:
@
text
@d120 1
a120 1
OpenBSD: roll your own?h
@


1.37
log
@web commit by dru () at 67.70.104.84:
@
text
@d108 3
a110 1
Importance: 3.2, Frequency: 1.4, Bloom: @@@@@@
a112 1
**Concept:**
d116 9
a124 1
**Estimated Time:**
@


1.36
log
@web commit by dru () at 67.70.104.84:
@
text
@d70 1
a70 1
**Concept:** Should we keep this objective which falls below both cutoff threshholds? If so, do we want them to do this during the install or go back into the installer utility afterwards? Or does the next objective make more sense to test than this one?
d79 1
a79 1
**Concept:** Should we keep this objective which falls below both cutoff threshholds? Does it make more sense to use the tools that come with other operating systems to make non-BSD partitions?
a88 1

d96 1
a99 1

@


1.35
log
@web commit by dru () at 67.70.104.84:
@
text
@d70 1
a70 1
**Concept:** Should we keep this objective? If so, do we want them to do this during the install or go back into the installer utility afterwards? Or does the next objective make more sense to test than this one?
d79 1
a79 1
**Concept:** Should we keep this objective? Does it make more sense to use the tools that come with other operating systems to make non-BSD partitions?
@


1.34
log
@web commit by dru () at 67.70.104.84:
@
text
@d79 1
a79 1
**Concept:**
@


1.33
log
@web commit by dru () at 67.70.104.84:
@
text
@d70 1
a70 2

**Concept:**
@


1.32
log
@web commit by dru () at 67.70.104.84:
@
text
@d51 1
a51 1
Importance: 3.3, Frequency: 1.5, Bloom: @@@@@@
@


1.31
log
@web commit by dru () at 67.70.104.84:
@
text
@d28 3
a30 1
**Estimated Time:** Varies by hardware, but completion of task will be too long for a lab scenario. Candidates may be asked to automate the required steps.
d45 3
a47 1
**Estimated Time:** 5 to 15 minutes
d49 1
a50 1
###  3. Use fdisk tool to modify or create partitions.
d53 3
d57 1
a57 1
**Concept:**
d61 1
d63 1
d65 1
a65 1
**Estimated Time:**
@


1.30
log
@web commit by dru () at 67.70.104.84:
@
text
@d31 1
a31 1
Importance: 3.5, Frequency: 1.4, Bloom: @@@@@@
d35 1
d37 1
d41 1
a41 1
**Estimated Time:**
d43 1
@


1.29
log
@web commit by dru () at 67.70.104.84:
@
text
@d30 1
a30 1
###  2. Use bsdlabel or disklabel to modify or create partitions.
d33 3
a35 1
**Concept:**
@


1.28
log
@web commit by dru () at 67.70.104.84:
@
text
@d28 1
a28 1
**Estimated Time:** Varies by hardware, but completion of task will be too long for a lab scenario. Candidate may be asked to automate the required steps.
@


1.27
log
@web commit by dru () at 67.70.104.84:
@
text
@d28 1
a28 1
**Estimated Time:** Varies by hardware, but completion of task will be too long for a lab scenario. Candidate may instead be asked which steps are required.
@


1.26
log
@web commit by dru () at 67.70.104.84:
@
text
@d12 1
a12 1
Importance: 3.6, Frequency: 1.7, Bloom: @@@@@@
d14 3
a16 1
**Concept:**
d20 9
a28 1
**Estimated Time:** Varies by hardware, but completion of task will be too long for a lab scenario.
@


1.25
log
@web commit by jpb () at 98.180.198.168: bloom tags
@
text
@d18 1
a18 1
**Estimated Time:**
@


1.24
log
@web commit by hubertf () at 94.16.0.16: jails better fit into VIRTUALIZATION, plus are not general
@
text
@d12 1
a12 1
Importance: 3.6, Frequency: 1.7
d21 1
a21 1
Importance: 3.5, Frequency: 1.4
d32 1
a32 1
Importance: 3.3, Frequency: 1.5
d44 1
a44 1
Importance: 2.5, Frequency: 1.2
d54 1
a54 1
Importance: 2.5,  Frequency: 1.3
d64 1
a64 1
Importance: 3.2, Frequency: 1.4
d75 1
a75 1
Importance: 2.8, Frequency: 1.4
d86 1
a86 1
Importance: 3.2, Frequency: 1.4
d97 1
a97 1
Importance: 2.8, Frequency: 1.4
d109 1
a109 1
Importance: 3.1, Frequency: 1.3
d120 1
a120 1
Importance: 3.3, Frequency: 1.9
d131 1
a131 1
Importance: 3.3, Frequency: 1.5
d142 1
a142 1
Importance: 3.6, Frequency: 1.3
d152 1
a152 1
Importance: @@@@@@I, Frequency: @@@@@@F
d163 1
a163 1
Importance: @@@@@@I, Frequency: @@@@@@F
d174 1
a174 1
Importance: 4.0, Frequency: 1.9
d184 1
a184 1
Importance: 3.5, Frequency: 1.4
d194 1
a194 1
Importance: 3.1, Frequency: 1.6
d204 1
a204 1
Importance: 3.7, Frequency: 2.2
d214 1
a214 1
Importance: 3.8, Frequency: 2.2
d243 1
a243 1
Importance: 3.8, Frequency: 2.0
d278 1
a278 1
Importance: 3.8, Frequency: 2.5
d303 1
a303 1
Importance: 3.3, Frequency: 1.7
d312 1
a312 1
Importance: 4.2, Frequency 3.0
d323 1
a323 1
Importance: 2.5, Frequency: 1.4
d335 1
a335 1
Importance: 2.4, Frequency: 1.2
@


1.23
log
@web commit by jpb () at 64.101.230.132:
@
text
@d218 2
d247 2
d282 2
@


1.22
log
@web commit by dru () at 67.70.104.84:
@
text
@d28 1
a28 1
Importance: @@@@@@I, Frequency: @@@@@@F
@


1.21
log
@web commit by dru () at 67.70.104.84:
@
text
@d134 1
a134 1
**Concept:** *BSDCG Note: This objective was removed at the 15/5/10 SME session. It should be considered for a Desktop exam.*
@


1.20
log
@web commit by dru () at 67.70.104.84:
@
text
@d100 1
a100 1
**Concept:** *BSDCG Note: This objective was removed at the 15/5/10 SME session. It should be considered for a Global Enterprise exam*
d107 1
d112 1
a112 1
**Concept:**
d117 1
d129 1
d134 1
a134 1
**Concept:**
d139 1
d161 1
d166 1
a166 1
**Concept:**
a169 1

d171 1
a179 2


d182 1
d186 1
a186 2

**Concept:**
d191 1
d315 1
d320 1
a320 1
**Concept:**
d325 1
d327 1
d332 1
a332 1
**Concept:**
d337 1
a337 1

@


1.19
log
@web commit by dru () at 67.70.104.84:
@
text
@d67 1
a67 1
**Concept:** *BSDCG Note: This objective was removed at the 15/5/10 SME session.
d95 1
d100 1
a100 1
**Concept:**
d105 1
@


1.18
log
@web commit by dru () at 67.70.104.84:
@
text
@d73 1
d83 1
@


1.17
log
@web commit by dru () at 67.70.104.84:
@
text
@d62 1
a62 1
<font color="#DCDCDC">
@


1.16
log
@web commit by dru () at 67.70.104.84:
@
text
@d62 1
a62 1
<font color="0xDCDCDC">
@


1.15
log
@web commit by dru () at 67.70.104.84:
@
text
@d62 1
a62 1
<font color="DCDCDC">
@


1.14
log
@web commit by dru () at 67.70.104.84:
@
text
@d62 1
a62 1
<font color="red">
@


1.13
log
@web commit by dru () at 67.70.104.84:
@
text
@d62 2
a63 1
<font color="red">###  6. Create or edit the device.hints or loader.conf file.
d67 1
a67 1
**Concept:**
@


1.12
log
@web commit by dru () at 67.70.104.84: red
@
text
@d62 1
a62 1
<span class="color=red">###  6. Create or edit the device.hints or loader.conf file.
d70 1
a70 1
**Estimated Time:**</span>
@


1.11
log
@web commit by dru () at 67.70.104.84:
@
text
@@


1.10
log
@web commit by jpb () at 98.180.198.168: Update import. and freq.
@
text
@d62 1
a62 1
###  6. Create or edit the device.hints or loader.conf file.
d70 1
a70 1
**Estimated Time:**
@


1.9
log
@web commit by jpb () at 98.180.198.168: Backfill previous content
@
text
@d12 1
a12 1
Importance: @@@@@@I, Frequency: @@@@@@F
a17 2


d21 1
a21 1
Importance: @@@@@@I, Frequency: @@@@@@F
a26 2


d32 1
a32 1
Importance: @@@@@@I, Frequency: @@@@@@F
d44 1
a44 1
Importance: @@@@@@I, Frequency: @@@@@@F
a50 2


d54 1
a54 2
Importance: @@@@@@I, Frequency: @@@@@@F

a59 2


d63 1
a63 1
Importance: @@@@@@I, Frequency: @@@@@@F
a69 2


d73 1
a73 1
Importance: @@@@@@I, Frequency: @@@@@@F
a79 2


d83 1
a83 1
Importance: @@@@@@I, Frequency: @@@@@@F
a89 2


d93 1
a93 1
Importance: @@@@@@I, Frequency: @@@@@@F
a99 2


d103 1
a103 1
Importance: @@@@@@I, Frequency: @@@@@@F
a109 2


d113 1
a113 1
Importance: @@@@@@I, Frequency: @@@@@@F
a119 2


d123 1
a123 1
Importance: @@@@@@I, Frequency: @@@@@@F
a129 2


d133 1
a133 1
Importance: @@@@@@I, Frequency: @@@@@@F
a139 2


a149 2


a160 1

d164 1
a164 2
Importance: @@@@@@I, Frequency: @@@@@@F

d175 1
a175 1
Importance: @@@@@@I, Frequency: @@@@@@F
a181 2


d185 1
a185 1
Importance: @@@@@@I, Frequency: @@@@@@F
a191 2


d195 1
a195 1
Importance: @@@@@@I, Frequency: @@@@@@F
a201 2


d232 11
a242 1
Importance: @@@@@@I, Frequency: @@@@@@F
d244 7
d252 1
a252 1
**Concept:**
d256 4
d261 1
a262 1
**Estimated Time:**
d265 8
a272 1
Importance: @@@@@@I, Frequency: @@@@@@F
d274 3
a277 1
**Concept:**
d281 1
d286 1
d288 1
a288 2
Importance: @@@@@@I, Frequency: @@@@@@F

a293 2


d297 1
a297 1
Importance: @@@@@@I, Frequency: @@@@@@F
a303 2


d307 1
a307 1
Importance: @@@@@@I, Frequency: @@@@@@F
a313 2


d317 1
a317 1
Importance: @@@@@@I, Frequency: @@@@@@F
a323 2


@


1.8
log
@web commit by jpb () at 98.180.198.168:
@
text
@d240 3
a242 1
Importance: @@@@@@I, Frequency: @@@@@@F
d244 3
d248 7
a254 1
**Concept:**
d258 1
d263 3
@


1.7
log
@web commit by jpb () at 98.180.198.168: Resort as original JTA
@
text
@d10 1
a10 1
INSTALLATION and SETUP
@


1.6
log
@web commit by dru () at 67.70.104.84: fat32
@
text
@d10 63
a73 2
### Configure custom kernel tunables to be enabled at boot time.
Importance: 4.0, Frequency: 1.9
d83 14
a97 2
### Configure system to mount remote network filesystems at boot.
Importance: 3.7, Frequency: 2.2
d107 3
a109 2
### Build and install system from source code.
Importance: 3.6, Frequency: 1.7
d119 3
a121 2
### Restore a corrupted boot sector.
Importance: 3.6, Frequency: 1.3
d131 3
a133 2
### Use bsdlabel or disklabel to modify or create partitions.
Importance: 3.5, Frequency: 1.4
d143 3
a145 2
### Password protect single user mode.
Importance: 3.5, Frequency: 1.4
d155 3
a157 2
### Display the order of startup steps/scripts to be run at boot time.
Importance: 3.3, Frequency: 1.9
d167 3
a169 2
### Create an internal package repository.
Importance: 3.3, Frequency: 1.7
d179 3
a181 2
### Use fdisk tool to modify or create partitions.
Importance: 3.3, Frequency: 1.5
d191 3
a193 2
### Install a boot manager.
Importance: 3.3, Frequency: 1.5
d203 3
a205 2
### Create or edit the device.hints or loader.conf file.
Importance: 3.2, Frequency: 1.4
d215 3
a217 2
### Create install script or configuration for unattended installation.
Importance: 3.2, Frequency: 1.4
d227 3
a229 2
### Configure BSD system for PXE booting.
Importance: 3.1, Frequency: 1.6
d239 3
a241 2
### Create an emergency repair disk.
Importance: 3.1, Frequency: 1.3
d251 2
a253 2
### Perform a 'headless' install using serial console.
Importance: 2.8, Frequency: 1.4
d255 1
a255 1
**Concept:** *BSDCG Note: This objective was removed at the 15/05/10 SME session.*
d263 3
a265 2
### Create an ISO installation image.
Importance: 2.8, Frequency: 1.4
d275 3
a277 2
### Compress a kernel.
Importance: 2.5, Frequency: 1.4
d287 3
a289 2
### Change Partition IDs to other BSD or non-BSD Ids.
Importance: 2.5, Frequency: 1.2
d299 3
a301 2
### Perform cross-platform building, such as using build.sh or 'make universe'.
Importance: 2.4, Frequency: 1.2
d311 2
d315 1
d317 1
d321 1
@


1.5
log
@web commit by dru () at 67.70.104.84:
@
text
@d170 1
a170 1
**Concept:** *BSDCG Note: This objective was removed at the 15/05/10 SME Session*
@


1.4
log
@web commit by jpb () at 64.101.230.132:
@
text
@a0 1

d170 1
a170 1
**Concept:**
@


1.3
log
@web commit by jpb () at 64.101.230.132:
@
text
@d1 1
d15 1
a15 1
Concept:
d17 1
a17 1
Practical:
d21 1
a21 1
Estimated Time:
d27 1
a27 1
Concept:
d29 1
a29 1
Practical:
d33 1
a33 1
Estimated Time:
d38 1
a38 1
Concept:
d40 1
a40 1
Practical:
d44 1
a44 1
Estimated Time:
d49 1
a49 1
Concept:
d51 1
a51 1
Practical:
d55 1
a55 1
Estimated Time:
d60 1
a60 1
Concept:
d62 1
a62 1
Practical:
d66 1
a66 1
Estimated Time:
d71 1
a71 1
Concept:
d73 1
a73 1
Practical:
d77 1
a77 1
Estimated Time:
d82 1
a82 1
Concept:
d84 1
a84 1
Practical:
d88 1
a88 1
Estimated Time:
d93 1
a93 1
Concept:
d95 1
a95 1
Practical:
d99 1
a99 1
Estimated Time:
d104 1
a104 1
Concept:
d106 1
a106 1
Practical:
d110 1
a110 1
Estimated Time:
d115 1
a115 1
Concept:
d117 1
a117 1
Practical:
d121 1
a121 1
Estimated Time:
d126 1
a126 1
Concept:
d128 1
a128 1
Practical:
d132 1
a132 1
Estimated Time:
d137 1
a137 1
Concept:
d139 1
a139 1
Practical:
d143 1
a143 1
Estimated Time:
d148 1
a148 1
Concept:
d150 1
a150 1
Practical:
d154 1
a154 1
Estimated Time:
d159 1
a159 1
Concept:
d161 1
a161 1
Practical:
d165 1
a165 1
Estimated Time:
d171 1
a171 1
Concept:
d173 1
a173 1
Practical:
d177 1
a177 1
Estimated Time:
d182 1
a182 1
Concept:
d184 1
a184 1
Practical:
d188 1
a188 1
Estimated Time:
d193 1
a193 1
Concept:
d195 1
a195 1
Practical:
d199 1
a199 1
Estimated Time:
d204 1
a204 1
Concept:
d206 1
a206 1
Practical:
d210 1
a210 1
Estimated Time:
d215 11
a225 1
Concept:
a226 1
Practical:
a229 1
Estimated Time:
@


1.2
log
@web commit by jpb () at 98.180.198.168: Section intro and concept descriptions.  Moved some tasks into other domains.  Deleted lowest scoring tasks.
@
text
@d8 2
@


1.1
log
@web commit by jpb () at 98.180.198.168:
@
text
@a0 1

d3 4
a6 7
### Compile a customized binary using ports, packages, or pkgsrc.
Importance: 4.2, Frequency 3.0

Concept:

Practical:

a8 2
Estimated Time:

a19 32
### Start or shutdown a jail.
Importance: 3.8, Frequency: 2.5

Concept:

Practical:



Estimated Time:

### Create and install a jail.
Importance: 3.8, Frequency: 2.2

Concept:

Practical:



Estimated Time:

### Prepare a host system for jails.
Importance: 3.8, Frequency: 2.0

Concept:

Practical:



Estimated Time:
a163 10
### Boot via the serial console.
Importance: 2.9, Frequency: 1.6

Concept:

Practical:



Estimated Time:
a197 11
### Create FAT32, NTFS, or other non-BSD partitions.
Importance: 2.5,  Frequency: 1.3

Concept:

Practical:



Estimated Time:

a219 11
### Configure a splash screen at boot.
Importance: 1.6, Frequency: 1.1

Concept:

Practical:



Estimated Time:

@
