Hi Ken - Thanks for the info - I did actually get the IPv4 only old glibc NIS/NISPLUS + rpcsvc headers generated by re-compiling with '--enable-obsolete-rpc --enable-obsolete-nsl' to enable rpcbind-0.2.4, libtirpc-1.0.1 and nfs-utils-2.1.1 working fine, to enable a simple 'sec=none' NFSv4 mount over a loopback device, anyway . - I don't actually need NIS or NISPLUS, so I have no idea if they actually work - probably use of Thorsten's libnfs-libnfs / your recipe is the only way ATM to get an actually working NIS / NISPLUS . I'm more interested in getting iSCSI + Radius working ATM . Thanks, Jason
On 01/06/2017, Ken Moffat <[email protected]> wrote: > On Sun, May 28, 2017 at 03:52:51PM +0000, Jason Vas Dias wrote: >> RE: On 28/05/2017, Ken Moffat <[email protected]> wrote: >> > Hmm, possibly Thorsten Kukuk wants people to use libnss_compat >> > https://github.com/thkukuk/libnss_compat/releases (I found that via >> > his glibc changelog entry on obsolete nsl where he mentions >> > https://github.com/thkukuk/libnsl is the replacement for NIS >> > functions. >> >> Aha ! That explains things. I guess the whole area is 'in transition' to >> the >> new fully IPv6 supporting NIS & RPC . I'll give Thorsten's new libnsl >> library >> a try. >> >> About the only serious stumbling block block I've come across in nearly >> 2 years of running "the latest git / scm tag" of every software package >> ala LFS >> has been this attempt to get RPC & NIS (& NFSv4) working . >> >> I guess we have to wait for glibc to integrate a fully functional >> replacement >> for the old IPv4 RPC + NIS code. >> >> Thanks anyway, >> Jason > > The whole area is at a state where maybe debian-unstable or > fedora-rawhide will be thinking about using it, but for BLFS it is > nowhere near ready. I'll be updating tickets when I'm back on my > main machine, this is just a note that I've got the (nfs2/3) client > working and I suppose the server ought to work too. But it is > messy. The build order (WITHOUT NIS or NIS+ or gssapi) is: > > libtirpc - needs to be a git version, and needs fixing for libnsl to > build. I'm using libtirpc-dd9c7cf (current HEAD) from > http://git.linux-nfs.org/?p=steved/libtirpc.git - that includes the > rpcbomb fix, and I run > sed -i 's/key_secret_is_set/key_secretkey_is_set/' src/libtirpc.map > from > https://sourceforge.net/p/libtirpc/discussion/637321/thread/fd73d431/ > > libnsl-libnsl-1.0.5 (he named his libs twice) > > libnss_compat-libnss_compat-1.2 > > BOth of those need ./autogen.sh and then I used > ./configure --prefix=/usr --sysconfdir=/etc/--disable-static > > rpcbind - no changes > > If by some mischance you need more rpcsvc/ headers for what you want > to build, rpcsvc-proto-1.2 needs the invocation of autoreconf in > autogen.sh changed, adding -fiv might be excessive but worked for > me. Fortunately I don't need any of: bootparam.h, bootparam_prot.h, > klm_prot.h, nfs_prot.h, rex.h, rstat.h, sm_inter.h - > So I didn't install it. Googling for rpc headers and trying to work > out what (other than old Sun code, or glibc) might provide them is not > fun. > > ĸen > -- > I live in a city. I know sparrows from starlings. After that > everything is a duck as far as I'm concerned. -- Monstrous Regiment > -- > http://lists.linuxfromscratch.org/listinfo/blfs-support > FAQ: http://www.linuxfromscratch.org/blfs/faq.html > Unsubscribe: See the above information page > -- http://lists.linuxfromscratch.org/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
