Re: Kernel calls, are they documented somewhere?

2000-11-02 Thread G. Adam Stanislav
On Thu, Nov 02, 2000 at 09:59:02AM +0100, Dag-Erling Smorgrav wrote: >Adam, it's really quite simple: if the carry flag is set, the syscall >failed, and the value returned is the errno (in your example, open(2) >returned 2, which is ENOENT, i.e. the file didn't exist). If it >succeeded, the value

Re: Kernel calls, are they documented somewhere?

2000-11-02 Thread Andrzej Bialecki
On Thu, 2 Nov 2000, G. Adam Stanislav wrote: > I do have the source code, and I have studied it, but it is uncommented. > And, it seems, not all of it is included. For example, there is a > /usr/src/lib/libc/sys/open.2 but no corresponding open.c. I have been > unable to find the source code for

Re: Kernel calls, are they documented somewhere?

2000-11-02 Thread Robert Nordier
G. Adam Stanislav wrote: > On Thu, Nov 02, 2000 at 12:12:02AM -0500, Michael Bacarella wrote: > >gcc does not generate code that can make FreeBSD system calls directly. > >Most system calls as we know them by the manual have corresponding > >wrappers in libc. See /usr/src/lib/libc if you have th

Re: Kernel calls, are they documented somewhere?

2000-11-02 Thread G. Adam Stanislav
On Thu, Nov 02, 2000 at 12:12:02AM -0500, Michael Bacarella wrote: >This isn't such a daunting task with grep. Source code cross referencers >can also help, but I don't use them nearly as often as I thought I would. Thanks for the grep suggestion. I think I found the source code for open() now (w

Re: Kernel calls, are they documented somewhere?

2000-11-02 Thread Dag-Erling Smorgrav
Michael Bacarella <[EMAIL PROTECTED]> writes: > gcc does not generate code that can make FreeBSD system calls directly. > Most system calls as we know them by the manual have corresponding > wrappers in libc. See /usr/src/lib/libc if you have the source installed. Wrong. The threaded C library (l

Re: Kernel calls, are they documented somewhere?

2000-11-01 Thread G. Adam Stanislav
On Thu, Nov 02, 2000 at 12:12:02AM -0500, Michael Bacarella wrote: >gcc does not generate code that can make FreeBSD system calls directly. >Most system calls as we know them by the manual have corresponding >wrappers in libc. See /usr/src/lib/libc if you have the source installed. I do have the

Re: Kernel calls, are they documented somewhere?

2000-11-01 Thread Michael Bacarella
On Wed, Nov 01, 2000 at 10:25:58PM -0600, G. Adam Stanislav wrote: gcc does not generate code that can make FreeBSD system calls directly. Most system calls as we know them by the manual have corresponding wrappers in libc. See /usr/src/lib/libc if you have the source installed. > Whatever secti

Kernel calls, are they documented somewhere?

2000-11-01 Thread G. Adam Stanislav
Are the system calls made via interrupt 0x80 documented somewhere? Whatever section 2 of man says does not work when making direct kernel calls. It only describes how the C library calls work. For example, open() returns -1 if the file is not open. But int 80h made in assembly language with EAX