News for hackers. Stuff that matters.
Re:Running Arbitrary Executables in AWS Lambda by pinkunicorn on Friday April 17, 2015 @09:04AM (#9394002)
This truly opens up a world of possibilities. My only itch in the wound is the lock into Amazon linux compatible executables. If they can run exe's compiled on a Ubuntu box, that would be awesome!
Re:Running Arbitrary Executables in AWS Lambda by sreque on Friday April 17, 2015 @10:21AM (#9394435)
Linux userland binary compatibility in general is surprisingly fragmented, thanks to the introduction of so symbol versions about a decade ago.

http://harmful.cat-v.org/software/dynamic-linking/versioned-...

https://refspecs.linuxfoundation.org/LSB_3.1.0/LSB-Core-gene...

I don't believe Amazon Linux is any worse than other Linux distributions in this regard. If you build a binary on an older Linux distribution (like CentOS 5), then there's a good chance it will run on most new distributions. The opposite is unfortunately not true.

Also, some libraries, like libcurl, don't seem to have consistent symbol versions across distributions. If your application links against libcurl, chances are you won't be able to create a single binary that runs on very many distributions.

Re:Running Arbitrary Executables in AWS Lambda by nivertech on Friday April 17, 2015 @11:00AM (#9394704)
I compiled a Golang static executable on Ubuntu uploaded it to AWS Lambda (which is Amazon Linux) and it works.

Didn't tried with C/C++.

Re:Running Arbitrary Executables in AWS Lambda by ranman on Friday April 17, 2015 @09:36AM (#9394163)
From an executable standpoint there's not a ton of lockin -- anything running a certain version of libc should behave the same way. You can compile an executable that will work on both Ubuntu and Amazon Linux.
Re:Running Arbitrary Executables in AWS Lambda by justincormack on Friday April 17, 2015 @09:06AM (#9394009)
You could run them under Wine, or use C#...