lxrun development
Since lxrun is fairly robust now, implementation of new system
calls has slowed down quite a bit. However, there are lots of
other aspects of lxrun that need work. If you'd like to help
with any of the following efforts, contact the people involved
or E-Mail
steven@ugcs.caltech.edu.
- ld-linux.so port to OSR5/UW2/UW7 --
By making a native ld-linux.so, there would no longer be a need
to execute lxrun explicitly -- the user could just run the Linux
app as if it were a native app. This is important to the seamless
integration of Linux apps into the SCO environments.
(Mike Davidson,
Steve Ginzburg)
- installation of lxrun --
Right now it's a major pain to install lxrun. Various files
have to be downloaded and installed in various places. This
process needs to be automated.
(Ron Record)
- Solaris x86 port & autoconf support --
Since the purpose of lxrun is to promote the free exchange
of software between systems, the more systems on which it
runs, the better. Andrew Gallatin successfully ported lxrun
v0.8.6 to Solaris. Work is currently under way to re-port
the current version of lxrun to Solaris, and also to make
lxrun's adaptation to the host system more robust using
GNU autoconf.
(James Macnicol)
- shared memory X11 --
Currently, all X applications that run under lxrun do so via
TCP/ip. This is because the shared memory scheme that Linux
uses for local communication between X apps and the X server
is incompatible with SCO's X servers. If we could devise a
way to bridge this gap, performance on lxrunned X apps would
improve dramatically.
Steve Ginzburg (steven@foo.net)