From: der.herr@hofr.at (Nicholas Mc Guire)
To: kernelnewbies@lists.kernelnewbies.org
Subject: System call vs POSIX call
Date: Fri, 17 Aug 2018 00:49:53 +0000 [thread overview]
Message-ID: <20180817004953.GA11799@osadl.at> (raw)
In-Reply-To: <137200.1534448689@turing-police.cc.vt.edu>
On Thu, Aug 16, 2018 at 03:44:49PM -0400, valdis.kletnieks at vt.edu wrote:
> On Thu, 16 Aug 2018 16:29:29 -0000, Nicholas Mc Guire said:
>
> > Note that you can do system calls directly with system() but that is
> > generaly not how you do it - you to through the glibc calls
> > which do some checks before invoking the actual system call.
>
> system() does a fork/exec of a process.
>
> syscall() issues an arbitrary system call, but all marshalling of
> parameters and return codes becomes your problem
yup - sorry - my bad - thats what I actually had in mind
but did not check.
thanks for your correction !
thx!
hofrat
prev parent reply other threads:[~2018-08-17 0:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-16 16:21 System call vs POSIX call Subhashini Rao Beerisetty
2018-08-16 16:29 ` Nicholas Mc Guire
2018-08-16 19:44 ` valdis.kletnieks at vt.edu
2018-08-16 21:05 ` Bernd Petrovitsch
2018-08-17 0:49 ` Nicholas Mc Guire [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180817004953.GA11799@osadl.at \
--to=der.herr@hofr.at \
--cc=kernelnewbies@lists.kernelnewbies.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).