Glibc 2.1 talks to it using a Unix-domain socket and falls back to
interpret nsswitch.conf directly if that doesn't work.
The easy fix for this mess is "don't even try to build Unix sockets as a
module". What for? You'll need it anyway, and it's a mere 9 kbytes.
If you really need that kind of space, build a stripped glibc -- the heap
of wide character functions which nobody needs(*) can be stripped off, for
instance. Note, however, that glibc's build process doesn't support this
out of the box...
(*) meaning, on an install/rescue floppy.
-- Matthias Urlichs | noris network GmbH | smurf@noris.de | ICQ: 20193661 The quote was selected randomly. Really. | http://www.noris.de/~smurf/-- If an elderly but distinguished scientist says that something is possible he is almost certainly right, but if he says that it is impossible he is very probably wrong. -- Arthur C. Clarke- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/