Date: Mon, 6 Jan 2003 11:48:47 -0600 From: wgrim@siue.edu To: Wes Peters <wes@softweyr.com> Cc: freebsd-hackers@freebsd.org Subject: Re: nsswitch help for you? Message-ID: <1041875327.3e19c17f7c1f1@webmail1.isg.siue.edu> In-Reply-To: <1041722581.17746.75.camel@zaphod.softweyr.com> References: <E18R5Ip-000KLt-00@cs.huji.ac.il> <1040799271.3e095627bbce3@webmail1.isg.siue.edu> <1041722581.17746.75.camel@zaphod.softweyr.com>
next in thread | previous in thread | raw e-mail | index | archive | help
All of that sounds great! I got the network setup at home to get -CURRENT downloadeded, but I might just do it once I get back to school (next Monday) where I have higher connection speeds. For now though, I can certainly take a look at several man pages, print them out and such. I'll try to keep ya updated. Oh, and you were right, the problem supposedly exists somewhere in the glibc libraries. I haven't taken a personal look yet, but supposedly dlopen() causes problems when called if the calling program isn't statically linked to libc. At least, I think I remember that synopsis correctly; it's been a while. Basically, the best I could get out of the synopsis is that the calling program calls a dlopen(), but it gets confused as to what is statically linked and what is not, and then it poops. Well, talk to you later man! Quoting Wes Peters <wes@softweyr.com>: > On Wed, 2002-12-25 at 06:54, wgrim@siue.edu wrote: > > Quoting Danny Braniss <danny@cs.huji.ac.il>: > > > > > what exactly do you want/need? > > > danny > > > > Sorry, I'll try to get as specific as I can with my currently limited > knowledge > > of the FBSD source code. > > > > Basically, I would like to know where I can find information on the > nsswitch > > protocol (if that is even such a thing): perhaps a document or standards > paper? > > The closest I've seen would be the nsswitch.conf man page from Solaris > or Linux. Read what functionality is provided, figure out how to make > that work on FreeBSD, write up your ideas, hack some code, ask for > reviews along the way. I'm certainl you'll find people who are > interested. > > > I will be downloading -CURRENT tomorrow so I can take a look at the current > > > nsswitch code, but is there anything you know right off hand that would > help me? > > Ick? ;^) > > While you're out digging up man pages and such, be sure to look up > gethostbyname_r, getpwuid_r, etc.; we've been needed these reentrant > versions for quite some time now. You will most likely find that a > proper implementation will provide the _r versions of these routines > then implement the static versions on top of the reentrant ones. > > > I'm sorry for the incompetence and don't want to clutter -hackers mailing > list > > any more than I have too, but I don't exactly know what types of questions > to > > even really ask you yet. If there is any general type of information you > have > > to help the learning curve of the kernel though, I'd appreciate it. > > There's a world of difference between incompetence and just starting > out. Please feel free to pester me for advice, moral support, reviews, > etc. I started filling out the complement of _r routines in the library > several years ago and quit when I got to getXbyY_r because the existing > code was so turgid and the task a bit too daunting for the time I had > available. Helping you finish it would lift a large load from my > FreeBSD psyche. :^) > > -- > > ------------------------------------------------- SIUE Web Mail To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1041875327.3e19c17f7c1f1>