FCoE requires /var and /usr unseparated from rootfs for network boot from SAN

Attempting to separate the /var and /usr filesystems from / (rootfs) in a FCoE network boot from SAN environment fails.

Leave /var and /usr in the / (rootfs) partition on the FCoE initiator disk. They must remain in the rootfs for a successful network boot via FCoE initiator.

Non rootfs partitions are mounted after /. The FCoE services require binaries that are contained in /usr and depend on /var for storing the PID info. Separating the partitions will prevent the boot.fcoe and boot.lldpad services from starting.

The boot.d/ configuration starts services in this order:

 
  /etc/rc.d/boot.d/S07boot.lldpad  -> Starts /sbin/lldpad
  /etc/rc.d/boot.d/S08boot.fcoe    -> Tries to start /usr/sbin/* fcoe binaries
  /etc/rc.d/boot.d/S10boot.localfs -> Runs 'mount -a' to mount /usr & /var

The boot.fcoe script will always fail on systems with a separate /usr filesystem since the executable are not yet available. During the boot, boot.lldpad fails with:

Starting lldpad:
 <notice -- Sep 17 23:16:37.710083000> start_daemon: execve
 (/sbin/lldpad) [ /sbin/lldpad -d ],...  ROOTFS_BLKDEV=/dev/vg00/rootlv
 _=/sbin/start_daemon DAEMON=/sbin/lldpad ]
 failed
 <notice -- Sep 17 23:16:37.712123000> 'boot.lldpad start' exits with
 status 1

And boot.fcoe fails with:

 <notice -- Sep 17 23:16:37.751224000> boot.fcoe start
 /usr/sbin/fcoeadm not installed
 Failed