nfs-root: strange library problem

I'm setting up a diskless client by getting the kernel via PXE and
root fs via nfs from a linux server. But after the nfs mount the
kernel does not start init. When I substitute the init (standart red
hat 9 /sbin/init) with a statically linked init then init gets
startetd! But everything else fails (everything else is
still dynamically linked).

I don't see where the problem could be since in the root nfs there is
a copy of a complete root fs of a redhat 9 install, including /lib
/bin /sbin /dev and so on. what could be missing?

If I make a chroot to the client nfs-root directory on the server I
can execute for example bash without problems. What could I try next?

In article <(E-Mail Removed)> ,
klaus thorn <(E-Mail Removed)> wrote:
> I'm setting up a diskless client by getting the kernel via PXE and
> root fs via nfs from a linux server. But after the nfs mount the
> kernel does not start init. When I substitute the init (standart red
> hat 9 /sbin/init) with a statically linked init then init gets
> startetd! But everything else fails (everything else is
> still dynamically linked).
>
> I don't see where the problem could be since in the root nfs there is
> a copy of a complete root fs of a redhat 9 install, including /lib
> /bin /sbin /dev and so on. what could be missing?
>
> If I make a chroot to the client nfs-root directory on the server I
> can execute for example bash without problems. What could I try next?

What are the options to the NFS mount? The relevant line in my /etc/exports
is this:

/nfs 192.168.1.24(rw,async,no_root_squash)

Maybe /lib/ld-linux.so has to be owned by root. You can try chowning it and
chrooting.

--
-eben (E-Mail Removed)m home.tampabay.rr.com/hactar

Hanlon's Razor: "Never attribute to malice that which can be
adequately explained by stupidity." Derived from Robert Heinlein