Given that:
- https://github.com/cloudius-systems/osv/issues/213
<https://www.google.com/url?q=https%3A%2F%2Fgithub.com%2Fcloudius-systems%2Fosv%2Fissues%2F213&sa=D&sntz=1&usg=AFQjCNFm9MZvq20-bJjZPElPE6wFQfk_qQ>
(closed)
- Allow running position-independent executables (PIE)
- https://github.com/cloudius-systems/osv/issues/352
<https://www.google.com/url?q=https%3A%2F%2Fgithub.com%2Fcloudius-systems%2Fosv%2Fissues%2F352&sa=D&sntz=1&usg=AFQjCNFtttjBKRg5qMkih4b63qicu1hq7Q>
-
Thread-local storage doesn't work in PIE
- https://github.com/cloudius-systems/osv/issues/190
<https://www.google.com/url?q=https%3A%2F%2Fgithub.com%2Fcloudius-systems%2Fosv%2Fissues%2F190&sa=D&sntz=1&usg=AFQjCNFMqyljHcHJWq9-4F08OFRKSeh2iA>
-
Allow running a single unmodified Linux executable
- https://github.com/cloudius-systems/osv/issues/212
<https://www.google.com/url?q=https%3A%2F%2Fgithub.com%2Fcloudius-systems%2Fosv%2Fissues%2F212&sa=D&sntz=1&usg=AFQjCNHxfOOMvmGpj6Yc_hDOgUYJ0WgVyw>
-
Allow running a statically-compiled Linux executable
shall we simply change this:
"Currently, OSv can only run executables in relocatable shared object
(".so") form. Support for running position-independent executables ("PIE")
is planned, but not yet available. Support for running a standard Linux
executable (non-relocatable dynamically linked executable) is also planned.
Support for running statically linked executables will be harder."
to
"Currently, OSv can run executables in relocatable shared object (".so")
form and as well as position-independent executables ("PIE") as long as
they do not use TLS. Support for running a standard Linux executable
(non-relocatable dynamically linked executable) is also planned. Support
for running statically linked executables will be harder." ?
Waldek
On Wednesday, April 10, 2019 at 2:30:48 PM UTC-4, Roman Shaposhnik wrote:
>
> Well, there's that whole "you need to convert your a.out into a.so"
> thing -- so I guess it is kind of a porting
>
> On Wed, Apr 10, 2019 at 11:23 AM Waldek Kozaczuk <[email protected]
> <javascript:>> wrote:
> >
> > I came across another unikernels-overview-type-of-writeup project on
> github - https://github.com/cetic/unikernels/blob/master/README.md.
> >
> > It has this description:
> > “OSv is particular; it allows porting various applications written in
> various languages to a unikernel by integrating some kernel functions
> built-in. Therefore, it is not as light as a fully compiled unikernel,
> however it provides support for many languages including Java, C, C++, Node
> and Ruby. ”
> >
> > How accurate is it? What does “porting” mean? Given OSv can run
> unmodified JVM so?
> >
> > Do you think there is some confusion in this area? Maybe outdated docs?
> >
> > --
> > You received this message because you are subscribed to the Google
> Groups "OSv Development" group.
> > To unsubscribe from this group and stop receiving emails from it, send
> an email to [email protected] <javascript:>.
> > For more options, visit https://groups.google.com/d/optout.
>
--
You received this message because you are subscribed to the Google Groups "OSv
Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
