Re: A module bug in 2.2.1?

Adam J. Richter (adam@yggdrasil.com)
Thu, 4 Feb 1999 10:44:45 -0800 (PST)


>You miss the point. They have a problem if the nscd is used. But the
>nscd comes with glibc 2.1. So there is no problem since not using
>wordexp is no problem with other library versions.

I don't know what "nscd" is, but I understood the point
that the shell was accidentally invoking some glibc2.1 facility
that had the side effect of causing the kernel to attempt to load
the unix socket module.

My point is that under the current cirumstances, we should
make sure that modutils continues to build under other C libraries.
Yes, we could use ifdef's and wordexp, but it seems to me that it
would be more maintainable just to use glob(3), which should work
everywhere. Admittedly, this is nitpicking about something that
will be three or four lines of code. As long as the solution is
still portable away from glibc2, I suppose that is good enough.

Adam J. Richter __ ______________ 4880 Stevens Creek Blvd, Suite 104
adam@yggdrasil.com \ / San Jose, California 95129-1034
+1 408 261-6630 | g g d r a s i l United States of America
fax +1 408 261-6631 "Free Software For The Rest Of Us."

-
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/