| 1 |
Paul de Vrieze <pauldv@××××××.nl> writes: |
| 2 |
|
| 3 |
> I know that, although one would probably still want a hurd that |
| 4 |
> complies to the linux interface, (provides the linux chasis) [...] |
| 5 |
|
| 6 |
What do you mean with "linux interface"? I guess you mean the system |
| 7 |
call interface of Linux. The Hurd itself cannot conform to that, |
| 8 |
because of it's design. |
| 9 |
|
| 10 |
In Linux - and in Unix in general - you can use the system services |
| 11 |
via system calls, a uniform way. This includes accessing files, |
| 12 |
creating processes, networking, etc. In the Hurd, there are seperate |
| 13 |
"servers" for such things and the services are used via RPCs. |
| 14 |
|
| 15 |
But since GNU aims POSIX compliance, of course, we have a POSIX |
| 16 |
interface , which is encapsulated in glibc. So, POSIX compliance |
| 17 |
programs should compile on GNU/Hurd just as they do on GNU/Linux - |
| 18 |
with few exceptions. |
| 19 |
|
| 20 |
In case you were referring to a binary compatibility - which means: |
| 21 |
having the same ABI - that does not exist at the moment although there |
| 22 |
have been some discussions on that topic on the Hurd lists. |
| 23 |
|
| 24 |
moritz |
| 25 |
-- |
| 26 |
moritz@×××××××××××××××.de - http://duesseldorf.ccc.de/~moritz/ |
| 27 |
GPG fingerprint = 3A14 3923 15BE FD57 FC06 B501 0841 2D7B 6F98 4199 |
Archives