From: "Albert Cahalan" <acahalan@gmail.com>
To: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
"Andrew Morton" <akpm@osdl.org>,
"Linus Torvalds" <torvalds@osdl.org>,
"Cal Peake" <cp@absolutedigital.net>, "Andi Kleen" <ak@suse.de>,
"Alan Cox" <alan@lxorguk.ukuu.org.uk>
Subject: Re: [CFT] Grep to find users of sys_sysctl.
Date: Fri, 20 Oct 2006 11:18:56 -0400 [thread overview]
Message-ID: <787b0d920610200818t1950d17y10a41957fd747c63@mail.gmail.com> (raw)
In-Reply-To: <m1wt6v2gts.fsf@ebiederm.dsl.xmission.com>
On 10/20/06, Eric W. Biederman <ebiederm@xmission.com> wrote:
> Jakub Jelinek <jakub@redhat.com> writes:
>
> > This assumes the binaries and/or libraries are not stripped, and they
> > usually are stripped. So, it is better to run something like:
> > find / -type f -perm /111 | while read f; do readelf -Ws $f 2>/dev/null | fgrep
> > -q sysctl@GLIBC && echo $f; done
>
> Russell King <rmk+lkml@arm.linux.org.uk> writes:
> > glibc on ARM _requires_ sys_sysctl for userspace ioperm, inb, outb etc
> > emulation.
>
>
> It looks like we have a small but interesting set of sysctl users.
>
> The list of files below is a composite from a number of systems I have
> access to, and the reply I have gotten so far. I'm still hoping to hear
> from other people so I can add some other users of sysctl to my list.
So does Linux now only support GLIBC apps? That's what your
grep seems to imply. At least one of the free Pascal compilers
does not use GLIBC. You won't find a GLIBC sysctl symbol in
any of the alternate C libraries (there are many) or even in libc5.
Running your grep on developer machines is highly biased
against legacy business apps.
Despite the desires of some fanatics, Linux does support an ABI
which is used by closed-source apps. Sometimes people even
lose their source code, perhaps via corporate reorganization.
I don't expect you plan to help anybody whose business depends
on some crufty old software...?
We have lots worse cruft if you want to go on a cleaning rampage.
We have old syscalls that can't handle modern data types.
next prev parent reply other threads:[~2006-10-20 15:18 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-18 18:23 sysctl Albert Cahalan
2006-10-18 18:27 ` sysctl David KOENIG
2006-10-18 18:31 ` sysctl Linus Torvalds
2006-10-18 18:52 ` sysctl Cal Peake
2006-10-18 19:12 ` sysctl Olaf Hering
2006-10-18 19:44 ` sysctl Andrew Morton
2006-10-18 21:06 ` sysctl Cal Peake
2006-10-19 4:41 ` [RFC] [PATCH] Improve the remove sysctl warnings Eric W. Biederman
2006-10-19 16:25 ` Cal Peake
2006-10-19 19:50 ` Alexey Dobriyan
2006-10-19 19:55 ` Cal Peake
2006-10-20 7:05 ` [CFT] Grep to find users of sys_sysctl Eric W. Biederman
2006-10-20 7:35 ` Andrew Morton
2006-10-20 12:54 ` Eric W. Biederman
2006-10-20 16:39 ` Andrew Morton
2006-10-21 10:23 ` Eric W. Biederman
2006-10-20 7:52 ` Russell King
2006-10-20 14:38 ` Eric W. Biederman
2006-10-20 15:18 ` Albert Cahalan [this message]
2006-10-21 10:53 ` Eric W. Biederman
2006-10-20 15:46 ` Bill Nottingham
2006-10-20 8:02 ` Jakub Jelinek
2006-10-20 13:41 ` Eric W. Biederman
2006-10-20 17:54 ` Marco Roeland
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=787b0d920610200818t1950d17y10a41957fd747c63@mail.gmail.com \
--to=acahalan@gmail.com \
--cc=ak@suse.de \
--cc=akpm@osdl.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=cp@absolutedigital.net \
--cc=ebiederm@xmission.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®