... commenting on bits and pieces of this thread...
On Tue, May 17, 2005 at 12:17:38AM +0100, Nix wrote:
> eee-ick. That'll really collide nastily with glibc's assumption that
> errno is located in thread-local storage, I fear.
It's sort of necessary (or some nasty trick is) because UML (re)maps its
code and text shareable into a number of different address spaces (each
UML process address space). errno can't be shared since different UML
threads running (system calls) simultaneously would tromp it. The
obvious thing to try to do is lock access to errno by putting a lock around
every system call. This is more horrible than what I decided to do
instead (locating errno in a per-thread private page).
> (Um, why is UML linking against libpcap? Or don't I want to know?)
There's a UML network transport which converts libpcap into UML eth0. You
install a sniffer into a UML filesystem, boot it up, give it access to
your network's traffic, and away you go.
Jeff
-------------------------------------------------------
This SF.Net email is sponsored by Oracle Space Sweepstakes
Want to be the first software developer in space?
Enter now for the Oracle Space Sweepstakes!
http://ads.osdn.com/?ad_id=7412&alloc_id=16344&op=click
_______________________________________________
User-mode-linux-user mailing list
User-mode-linux-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-user
