My experience with this sort of thing is that you have a Windows DHCP server which paradoxically requires you to add a link in your filesystem. It serves up the incorrect path for your filesystem. It hands out /opt/ltsp/i3860000 instead of /opt/ltsp/i386. All you need to do is add a symbolic link. I can't remember off-hand if you need to check NFS exports - try it and see.
Watch your client boot messages - it tells you the correct name.
Smile and nod, though- it's a Win DHCP issue.
Angus Carr.
Message: 6 Date: Mon, 05 Apr 2004 12:10:55 -0500 From: Brandon Kovach <bkovach lrhs greene-r8 k12 mo us> Subject: [K12OSN] Client won't boot, but getting close To: k12osn redhat com Message-ID: <4071931F 6060605 lrhs greene-r8 k12 mo us> Content-Type: text/plain; charset=us-ascii; format=flowed
I have a single NIC setup going. I have the client requesting an IP addy from a DHCP server, the DHCP server is talking with the K12 server, but the client says that it failed to mount the root filesystem from <ip addy>:/opt/ltsp/i386: Permission Denied.
ANyone know what that means?
Brandon Kovach New to this whole thing
_______________________________________________ K12OSN mailing list K12OSN redhat com https://www.redhat.com/mailman/listinfo/k12osn For more info see <http://www.k12os.org>