On Wed, Jun 18, 2008 at 11:29 AM, James G. Sack (jim) <[EMAIL PROTECTED]> wrote: > Carl Lowenstein wrote: >>.. >> Answer to second question is rather verbose. Well, 37 lines, >> including the command synopsis. >> >> $ mkdir /tmp/foo; cd /tmp/foo >> $ rpm2cpio /data/transfer/opera-9.50.gcc4-shared-qt3.x86_64.rpm | cpio -idv >> $ cd /tmp/foo/usr/lib/opera/9.50 >> $ ldd opera >> linux-vdso.so.1 => (0x00007fffe91fe000) > .. >> >> The only non-present thing is "linux-vdso.so.1" as I see it. >> > > I don't know what that entry is -- my output is the same (different load > address, though) > linux-vdso.so.1 => (0x00007ffff31fd000)
Google is (somewhat) your friend. First I learned that vdso.so is built into the kernel, and has been for a couple of years. Then I learned what the name means, from: <http://kernelnewbies.org/KernelGlossary> "Virtual Dynamically-linked Shared Object, a kernel-provided shared library that helps userspace perform a few kernel actions without the overhead of a system call, as well as automatically choosing the most efficient syscall mechanism." Never a dull moment. carl -- carl lowenstein marine physical lab u.c. san diego [EMAIL PROTECTED] -- [email protected] http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
