News for hackers. Stuff that matters.

A comment on C library system-call wrappers, or the lack thereof. Parent comment

Re:C library system-call wrappers, or the lack thereof by masklinn on Wednesday November 14, 2018 @08:03AM (#18449513)
The biggest advantage is that it lets other OS easily impersonate linux e.g. SmartOS or Windows can provide kernel-level "linux persona" and have an unmodified linux userland run on top.
[ Parent | on HN ]
Re:C library system-call wrappers, or the lack thereof by int0x80 on Wednesday November 14, 2018 @10:15AM (#18450405)
They can do right now. Both the API and ABI are very rarely (read never but very problematic bugs or similar) broken in a backwards way.
[ Parent | on HN ]
Re:C library system-call wrappers, or the lack thereof by masklinn on Wednesday November 14, 2018 @11:26AM (#18451058)
That's my point. It's only possible with Linux because Linux provides a stable kernel ABI. You can't impersonate Windows or OSX the same way.
[ Parent | on HN ]
Re:C library system-call wrappers, or the lack thereof by int_19h on Wednesday November 14, 2018 @06:35PM (#18455322)
But you can impersonate Windows by providing your own implementation of the Kernel32 API. What's the essential difference between that, and emulating syscall API?
[ Parent | on HN ]
Re:C library system-call wrappers, or the lack thereof by int0x80 on Wednesday November 14, 2018 @11:30AM (#18451096)
Ahh sorry, I understood the other way around :)
[ Parent | on HN ]