On Sat, Feb 21, 2015 at 02:31:20PM -0600, Bruce Dubbs wrote: > > I did a test of nfs a week or two ago and didn't have any problems, I'll > test it when I get to it. > I guess that was when you updated BLFS to 1.3.2, and by that time you had moved LFS to glibc-2.21. So in theory it should all work.
> > Also, should we (both LFS and BLFS) assume that our kernels support > >ipv6 ? > > I do have ipv6 enabled in my kernels, but do not use it at all. I do not > assign any ipv6 addresses to any interfaces. > > -- Bruce For the moment, the messages might merely be "annoying" rather than critical. I disabled the bootscript and commented out my fstab entry for /sources. Ran 'strace rpc.statd', waited, killed it. It failed to open /var/run/nscd then seemed to go into a loop with 'Transport endpoint is not connected' messages (since I'm not running it as a daemon under strace, it might even be working). Tried mkdir /var/run/nscd and repeated, then killed it. Did not seem to make any difference to the strace output. Wondered if it might eventually time out, so ran 'time /etc/rc.d/init.d/nfs-client start' and it started immediately. Wondered if it was now ok, re-enabled everything, it hangs forever trying to start this. <sigh/> Then I wondered if /var/run was being trashed because it is a link to /run. Interestingly, if I mount the new system at /mnt/lfs I can see that there are some files and directories (cups,dbus,udev) obviously from the host. Added a line 'mkdir -p /var/run/nscd' to the bootscript, no joy, it is still hanging. ĸen -- Nanny Ogg usually went to bed early. After all, she was an old lady. Sometimes she went to bed as early as 6 a.m. -- http://lists.linuxfromscratch.org/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
