linux-kernel - Re: FATAL: kenrel too old

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <20111026.191605.568124603250227730.davem@davemloft.net>
Date:	Wed, 26 Oct 2011 19:16:05 -0400 (EDT)
From:	David Miller <davem@...emloft.net>
To:	michael.hebenstreit@...el.com
Cc:	linux-kernel@...r.kernel.org
Subject: Re: FATAL: kenrel too old - message

From: "Hebenstreit, Michael" <michael.hebenstreit@...el.com>
Date: Wed, 26 Oct 2011 23:04:04 +0000

> Can someone explain me why even an ldd on a dynamic executable gives
> a "kernel too old"? I understand that linking to a gcc that does not
> support the kernel causes this problem at runtime, but why does ldd
> fail? Are there other ways to diagnose this?

ldd is not a seperate tool on it's own.

It is implemented by executing the program under the dynamic linker
with special options and/or environment variables set which make the
dynamic linker print out the information requested.

Have a look at /usr/bin/ldd, it's just a shell script.

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/