«

Hi,

There are more than 1000 defined system calls in the Unix standard
specification, however, a majority of them are optional and the
availability of system calls are dependent on the OS implementation
itself.

The question I have is: How do you determine which system calls are
available on any Unix/Linux machine?

The same question goes for determening available C library functions
on any Unix/Linux machine?

Best regards

(markus) wrote:

> The question I have is: How do you determine which system calls are
> available on any Unix/Linux machine?
>
> The same question goes for determening available C library functions
> on any Unix/Linux machine?

If the computer has a conforming C implementation, _all_ C library
functions must be available; otherwise it simply isn't a C
implementation.
As for determining what is present, that's OS-specific, hence off-topic
on comp.lang.c.

Richard

Richard Bos <> wrote:
> (markus) wrote:
> > The question I have is: How do you determine which system calls are
> > available on any Unix/Linux machine?

You don't. It's none of your business. It's the C library's business to
interface between you and the system calls.

But if you wanted to, you would read the kernel's syscall
implementation list in the source code.

> > The same question goes for determening available C library functions
> > on any Unix/Linux machine?

> If the computer has a conforming C implementation, _all_ C library
> functions must be available; otherwise it simply isn't a C
> implementation.

Well, whther the functions work or not also enters into it. However ...

> As for determining what is present, that's OS-specific, hence off-topic
> on comp.lang.c.

In the last 20 years, I have never seen anything that is on topic on
comp.lang.c, which is why I have avoided going there like the plague
during the last 20 years. If you want language lawyery, it's an
excellent place to hang out and pick nits.

It's sort of like Wittgenstein. Anything you asked him he told you was
some other disciplines kind of problem, not philosophy.

Peter

markus wrote:
>
> There are more than 1000 defined system calls in the Unix standard
> specification, however, a majority of them are optional and the
> availability of system calls are dependent on the OS implementation
> itself.
>
> The question I have is: How do you determine which system calls are
> available on any Unix/Linux machine?
>
> The same question goes for determening available C library functions
> on any Unix/Linux machine?

ALL the functions specified in the ISO C standard should be
available on any hosted machine. Anything else is system
dependant and off-topic on c.l.c.

Thus code that uses such non-standard calls should be in an
isolated system dependant module, and discussed only on system
specific newsgroups. Above all they should not be cross-posted to
groups where they are OT.

--
Chuck F () ()
Available for consulting/temporary embedded and systems.
<http://cbfalconer.home.att.net> USE worldnet address!

(markus) writes:

> Hi,
>
> There are more than 1000 defined system calls in the Unix standard
> specification, however, a majority of them are optional and the
> availability of system calls are dependent on the OS implementation
> itself.
>
> The question I have is: How do you determine which system calls are
> available on any Unix/Linux machine?
>
> The same question goes for determening available C library functions
> on any Unix/Linux machine?

That is what the "configure" script in most UNIX source code packages
does. If you tell us what you are trying to do, you might get a more
useful answer.

(markus) wrote:
# Hi,
#
# There are more than 1000 defined system calls in the Unix standard
# specification, however, a majority of them are optional and the
# availability of system calls are dependent on the OS implementation
# itself.
#
# The question I have is: How do you determine which system calls are
# available on any Unix/Linux machine?

Trial and error, unfortunately, is too often the case. On a proper system you should be
able to look at /usr/share/man/man2 and man3 or the section 2 and 3 portion of xman to
get a rough idea. However many systems anywhere are inadequately documented. You can also
try nm /usr/lib/libc.so or similar files.

--
SM Ryan http://www.rawbw.com/~wyrmwif/
Mention something out of a Charleton Heston movie, and suddenly
everybody's a theology scholar.

(markus) wrote in message news:<. com>...
> Hi,
>
> There are more than 1000 defined system calls in the Unix standard
> specification, however, a majority of them are optional and the
> availability of system calls are dependent on the OS implementation
> itself.
>
> The question I have is: How do you determine which system calls are
> available on any Unix/Linux machine?
>
> The same question goes for determening available C library functions
> on any Unix/Linux machine?
>
> Best regards

you can try
apropos '(3)' for library functions
apropos '(2)' for system calls

This should give you a list, at least for those functions that have a
man page in the system I suppose...

P.T. Breuer wrote:

> In the last 20 years, I have never seen anything that is on topic on
> comp.lang.c, which is why I have avoided going there like the plague
> during the last 20 years. If you want language lawyery, it's an
> excellent place to hang out and pick nits.


Pure lies. We handle many questions and problems each day, as long as
they fit the topicality of the newsgroup.



Brian Rodenborn

Default User <> wrote:
> P.T. Breuer wrote:
>
> > In the last 20 years, I have never seen anything that is on topic on
> > comp.lang.c, which is why I have avoided going there like the plague
> > during the last 20 years. If you want language lawyery, it's an
> > excellent place to hang out and pick nits.

> Pure lies. We handle many questions and problems each day, as long as
> they fit the topicality of the newsgroup.

There you are!

Peter

P.T. Breuer wrote:

> Default User <> wrote:
> > P.T. Breuer wrote:
> >
> > > In the last 20 years, I have never seen anything that is on topic
> > > on comp.lang.c, which is why I have avoided going there like the
> > > plague during the last 20 years. If you want language lawyery,
> > > it's an excellent place to hang out and pick nits.
>
> > Pure lies. We handle many questions and problems each day, as long
> > as they fit the topicality of the newsgroup.
>
> There you are!

Quite a non-sequitur. Do you deny that we (comp.lang.c) handle many
questions and problems each day? Do I need to post examples and make
you look foolish?




Brian Rodenborn