Bugzilla Bug 78825

Install a system according the handbook using the stage3 tar ball from the
2004.3 release. The system does not have a /etc/devfs.d directory. This
prevents devfsd from starting and the kernel panics not finding /dev/sd4 (/)

Once the cirectory is created, devfsd startes and the kernel can find / and
continue the boot.

Reproducible: Always
Steps to Reproduce:
1. Install system per handbook instructions
2. reboot

Actual Results:  
 * Starting devfsd...Started device management daemon v1.3.25 for /dev
error opening file: "/etc/devfs.d"      No such file or directory
  [ !! ]

 * Activating (possible) swap...  [ ok ]
 * Remounting root filesystem read-only (if necessary)...  [ ok ]
 * Checking root filesystem...fsck.ext3: No such file or directory while trying
to open /dev/sda4
/dev/sda4: 
The superblock could not be read or does not describe a correct ext2
filesystem.  If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
    e2fsck -b 8193 <device>

 * Filesystem couldn't be fixed :(
  [ !! ]

Give root password for maintenance
(or type Control-D for normal startup):

Expected Results:  
/etc/devfs.d is created and system should boot correctly

I have not tested other stage tarballs or other releases

changed devfsd to run 'keepdir' instead of 'dodir' on /etc/devfs.d