Hello,
[ please Cc: me, I'm not subscribed to this list ]
[ Note: I'm cutting and pasting from the lists' archive ]
> The kernel code seems to have severe race conditions and the
> userspace seems to be bitten by a compareable number of security
> incidents as e.g. a stabel debian with a correspo
>Suggestions on how to properly figure out which libraries things must
link
>against (especially involving libraries which may or may not be present,
>such as libi386 and libm387 - especially the latter) would be
appreciated.
>
> well, libi386 is linked into applic
On Tue, Oct 29, 2002 at 01:28:44AM -0700, Joel Baker wrote:
>
> Really what I'm trying to find is a way to examine a dump of the object, or
> maybe trying to build a static version from the .so, and finding out what
> symbols are, and are not, declared in the library ('are not' meaning we
> need t
On Tue, Oct 29, 2002 at 07:22:08PM +1100, matthew green wrote:
>
>Okay. So it's a matter of historical FUBARism - which means I should, at
>the very least, have a FIXME to find some way to fix it, and not turn
>off the warnings.
>
>NetBSD arguments aside, this information *s
Okay. So it's a matter of historical FUBARism - which means I should, at
the very least, have a FIXME to find some way to fix it, and not turn
off the warnings.
NetBSD arguments aside, this information *should* be used on Debian, simply
because it becomes very important when
On Tue, Oct 29, 2002 at 06:05:50PM +1100, matthew green wrote:
>
>Need someone with more familiarity with NetBSD's intricacies to assist on
>this one. Currently, lintian is throwing a spew of a single error (one per
>library, in both libc12 and libc12-dbg), based on the fact that Ne
Need someone with more familiarity with NetBSD's intricacies to assist on
this one. Currently, lintian is throwing a spew of a single error (one per
library, in both libc12 and libc12-dbg), based on the fact that NetBSD,
unlike Linux, does not have every library dependant on libc (a
Need someone with more familiarity with NetBSD's intricacies to assist on
this one. Currently, lintian is throwing a spew of a single error (one per
library, in both libc12 and libc12-dbg), based on the fact that NetBSD,
unlike Linux, does not have every library dependant on libc (and, in Linux,
li
8 matches
Mail list logo
