Problems of New Linuxulator I Have Known

[Intron is my alias on the Internet]

1. Many options of clone(2) are not correctly implemented, some of
    which may cause application crash when it wants to clone
    memory-independent process.

2. TLS (Thread Local Storage) support in clone(2), set_thread_area(2)
    and get_thread_area(2) doesn't conform to Linux 2.6.x, which can
    damage stack of Linux application using NPTL (Native  POSIX  Threads
    Library).

    Of course, to obtain the conformation, FreeBSD native GDT must be
    rearranged. But Linux NPTL is quite essential for modern Linux
    applications.

3. wakeup_one(9) instead of wakeup(9) should be used for futex(2) to
    wake up a single sleeping thread.

4. Some options of clock_gettime(2) actually can be implemented, though
    FreeBSD native implementation is different from Linux's.

5. Code style problems: member naming of structure, macro naming,
    function naming, encapsulation for queue(3) and so on.

In a word, may ORACLE 10g for Linux be able to run under FreeBSD soon.

------------------------------------------------------------------------
                                                From Beijing, China

Alexander Leidinger wrote:

> Quoting Divacky Roman <xdivac02 at stud.fit.vutbr.cz> (from Fri, 25 Aug  2006 
> 10:47:55 +0200):
> 
>> I have some more fixes uncommited which might fix the acroread.
> 
> For the curious:  
> http://www.leidinger.net/FreeBSD/linuxolator/013_linuxolator_final_uncommi 
> tted.diff
> 
> Bye,
> Alexander.
> 
> -- 
> In any country there must be people who have to die.  They are the
> sacrifices any nation has to make to achieve law and order.
> 		-- Idi Amin Dada
> 
> http://www.Leidinger.net    Alexander @ Leidinger.net: PGP ID = B0063FE7
> http://www.FreeBSD.org       netchild @ FreeBSD.org  : PGP ID = 72077137
>