Date: Fri, 30 Dec 1994 16:03:14 -0800 From: "Jordan K. Hubbard" <jkh@time.cdrom.com> To: Wankle Rotary Engine <wpaul@skynet.ctr.columbia.edu> Cc: kuku@acds, freebsd-hackers@freebsd.org Subject: Re: ypserv for FreeBSD? Message-ID: <3844.788832194@time.cdrom.com> In-Reply-To: Your message of "Fri, 30 Dec 94 18:22:20 EST." <199412302322.SAA01029@skynet.ctr.columbia.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
> Compile yes, work yes! :) Actually, it seems to work fairly well. > I have the ypserv-0.11 package up on a 2.1.0-Development system right > now. It does seem to work with FreeBSD's client-side YP stuff, though > I think FreeBSD's client-side stuff still needs a little work (ps > sometimes reports that processes owned by me are owned by 'daemon' and > ls, in some cases, says that files owned by me are owned by 'root' -- I > think I smell a library problem). > > What I don't have working yet is yppasswd and yppasswdd, though I > have the Linux versions of those too. I also don't know if this > ypserv package supports yp-xfr. I haven't tried building the server > in the yps-0.21 package yet, though that's next on my agenda. > > The question is, do we really want to port these over and use them? > It shouldn't be too much trouble (I want to convert them from gdbm to db > so it won't be necessary to ship libgdbm with FreeBSD), but I think this > stuff is GPL'ed. I could live with that. I could really use a complete yp* set so that I could just create users on freefall and have thud mirror this. Right now, it's just an admin pain! Jordan
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3844.788832194>