I am also seeing this(lockd) on my built-from-scratch boxes, so it isnt just a
Dell boxen prob.

The nfs lockd part is a duplicate of #12316.

As of automounter:

At first boot after installation I do get the following messages:

insmod: insmod: a module named autofs already exists
insmod: insmod autofs failed

The first of these two messages is only shown at the fist boot.

The message is shown right after "Initializing random number generator". So I do
suppose that this happens in S25netfs (when in runlevel 3).

At shutdown, the exact message is:

Stopping automounter [OK]
Stopping automounter (attempt 2) /usr/sbin/automount: no process killed

I did also upgrade to the latest initscripts (that where published when updating
XFree86 in beta2). Same result.

Shutting down autofs is always tricky, especially when filesystems controlled
by autofs are busy.  This should be improved somewhat in the current release,
though the busy filesystem problem remains not completely solved.

changed component to autofs.

on AXP in beta 3, on boot it throws simmilar messages about not being able to 
insert the module into the kernel. But when you log in, it is running and yes 
the file systems are auto-mountable when they are called.

Kurt Ludwig

I can't reproduce this in beta4. lockd shutdown works
OK.

This is fixed in Beta 5.  Thanks!

Okay, closing the bug.