Why does klibc make such a difference for v86d?

Question

I decided to use uvesafb again, having built it for the first time in 2010. However, it gave a horribly corrupted image with v86d from the repos. The only way I can get the console to look as good as it did in 2010 is to link v86d against klibc. Making the klibc-2.0.2 package for that purpose today was really annoying.
Before Arch used busybox, some things *needed* klibc. They would simply crash if you tried to link them against glibc and run them in early userspace without the root directory being mounted. But I'm at a loss for what is going on here -- v86d runs with or without klibc but having it linked to klibc makes it better (at least on an old ATI Rage Mobility M3).

Answer 1

I don't know if it's a good thing, but the fact is that process names are case-sensitive, so that two processes, respectively named "Safari" and "safari", could +in principle+ be running at the same time.
To be sure about that, I wrote a very short script that I saved as a stay-open application under the name "safari" and launched while the "Safari" browser was already running. Then I executed the following statement in the Script Editor:
*tell application "Finder" to return processes*
--> {…, application process "Safari" of application "Finder", application process "safari" of application "Finder", …}
Maybe you might find [this article|http://lambda-the-ultimate.org/node/1114] interesting.