I performed a basic installation of FreeBSD 5.4 on SULA, added MySQL packages and the NetBackup software. It is now ready for development prior to production use as a database server.

Some minor setbacks when dealing with this particular hardware. This PE1850 has 8GB of RAM, and FreeBSD doesn’t normally see anything above 4GB without the Physical Address Extension (PAE) kernel options.

• PAE extensions must be compiled into the kernel to use all the RAM.

• PAE requires that the kernel be statically linked — that is, no loadable kernel modules.

• IPFilter is not included in the base kernel by default, so it must be added to the kernel config file before making. (Or OpenBSD pf, if that is what you’re using).

Jumpstart is completing on Lumana, which will become the SCT Luminis server.

There are a few new things coming with this Jumpstart:

• Solaris 9, release 9-04 (required for supporting the SunFire V440).

• A volume manager layout for SVM disks. The new layout derives the MD device number from the underlying raw disk device number. The target number is used for the tens and the slice number is used for the ones: c1t0d0s5 becomes d5, c1t1d0s5 becomes d15. Mirrored devices are still the only things supported, and the mirror device is taken from 7+the target number of the second disk: if the previous two were mirrored, the mirror meta device would be d85. Swap is always d8, d18, and d78, since it’s impossible for any other slices to come up with a d*8 meta device name.

There are a few rc*.d scripts that need to be moved out of the way after the patches are applied now.

PAU has had a basic installation done, with Veritas Foundation, NetBackup, and the Forte developer tools added on after Jumpstart. It is using LUN 0 of the second half of each of the new Xserve RAID units for its data partition (see Fibre Channel SAN in the TWiki documentation).