In article <[EMAIL PROTECTED]>,
Maxime Henrion <[EMAIL PROTECTED]> wrote:
>
> When ldconfig is invoked without any parameters, the shared library
> cache is reseted to the contents of /usr/lib only. I think such a
> behaviour isn't very useful, especially when one knows that a lot of
> people come to FreeBSD after having used Linux. The first time they get
> an error message like "foo.so not found", they, nearly automatically,
> run ldconfig and so screw up their shared library cache.
> Is there a special reason why ldconfig behaves this way ? And is
> there any application that rely on that behaviour ? This would at least
> estonish me. That's why, i wanted to suggest that ldconfig prints a
> usage screen when invoked without parameters, or else that it performs a
> default and safe action, like a refresh (ldconfig -R).
I agree with you. The default action should be the same as "-R".
Don't worry, there aren't any applications that rely on the current
behavior.
> If it happens that what I say make sense, and that the two
> requirements above are met (see the two questions), i'll be happy to
> submit a patch.
Great. If you'll make the patch, I'll review it and commit it.
John
--
John Polstra [EMAIL PROTECTED]
John D. Polstra & Co., Inc. Seattle, Washington USA
"Disappointment is a good sign of basic intelligence." -- Chögyam Trungpa
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
