From: Jeff Dike <jdike@karaya.com>
To: ebiederm@xmission.com (Eric W. Biederman)
Cc: Oleg Drokin <green@namesys.com>,
Linus Torvalds <torvalds@transmeta.com>,
Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux 2.5.60
Date: Wed, 12 Feb 2003 06:49:49 -0500 [thread overview]
Message-ID: <200302121149.GAA01822@ccure.karaya.com> (raw)
In-Reply-To: Your message of "12 Feb 2003 01:11:23 MST." <m17kc5yl3o.fsf@frodo.biederman.org>
ebiederm@xmission.com said:
> Just for throwing out suggestions, UML can easily avoid using glibc
> altogether as it is already intimate with the system call layer.
Easily? As in write my own system call wrappers? And how is UML intimate
with the system calls, anyway? It is no more intimate with the host's
system calls than any other app.
It also uses some smaller higher-level pieces of libc (printf early in boot,
readdir et al in hostfs, etc).
> Or it can use the linker to play games with symbol names to move the
> kernel off into it's own separate name space.
Maybe, I'm not expert enough with the linker to do that.
> This sounds like a good opportunity to figure out which makes most
> sense and future proof UML.
My current thinking is that I will bundle all the userspace code into a
single object which then gets linked (-r IIRC) against libc. That should
resolve all libc references, at which point I can link it into the kernel,
and I think there won't be any conflicts.
Jeff
next prev parent reply other threads:[~2003-02-12 11:46 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-10 19:08 Linux 2.5.60 Linus Torvalds
2003-02-10 20:41 ` Maciej Soltysiak
2003-02-10 21:06 ` Linux 2.5.60 Compile error James Lamanna
2003-02-10 21:38 ` Kevin Corry
2003-02-10 22:50 ` Muli Ben-Yehuda
2003-02-10 21:52 ` Dave Jones
2003-02-11 0:12 ` Another " Vlad@geekizoid.com
2003-02-11 5:21 ` Anthony J. Breeds-Taurima
2003-02-10 21:11 ` Linux 2.5.60 Stephen Hemminger
2003-02-10 21:25 ` James Lamanna
2003-02-10 22:54 ` Linus Torvalds
2003-02-10 20:46 ` 2.5.60: JFS no longer compiles with gcc 2.95 Adrian Bunk
2003-02-10 21:43 ` James Lamanna
2003-02-11 7:27 ` Adrian Bunk
2003-02-12 14:52 ` [PATCH - 2.5.60] " Dave Kleikamp
2003-02-12 15:04 ` Adrian Bunk
2003-02-12 15:42 ` Dave Kleikamp
2003-02-12 16:22 ` Andreas Schwab
2003-02-10 22:21 ` Linux 2.5.60 John Cherry
2003-02-11 7:08 ` Oleg Drokin
2003-02-11 7:38 ` Linus Torvalds
2003-02-12 8:11 ` Eric W. Biederman
2003-02-12 11:49 ` Jeff Dike [this message]
2003-02-13 23:25 ` Werner Almesberger
2003-02-11 15:16 ` Zephaniah E. Hull
2003-02-11 22:47 ` Andrew Morton
2003-02-11 22:54 ` Andrew Morton
2003-02-14 16:56 ` Zephaniah E. Hull
2003-02-11 16:23 ` Russell King
2003-02-11 17:06 ` Linus Torvalds
2003-02-12 2:47 ` David S. Miller
2003-02-11 16:44 ` 2.5.60: arlan.c no longer compiles Adrian Bunk
2003-02-11 23:08 ` Andrew Morton
2003-02-11 18:16 ` 2.5.60: sim710.c doesn't compile Adrian Bunk
2003-02-11 18:21 ` James Bottomley
2003-02-11 22:00 ` Linux 2.5.60 Rudmer van Dijk
2003-02-12 10:05 ` Ingo Oeser
-- strict thread matches above, loose matches on Subject: below --
2003-02-13 4:12 Jeff Dike
2003-02-13 8:19 ` Oleg Drokin
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=200302121149.GAA01822@ccure.karaya.com \
--to=jdike@karaya.com \
--cc=ebiederm@xmission.com \
--cc=green@namesys.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.com \
/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