From: "Андрій Мішковський" <mishok13@gmail.com>
To: linux-c-programming@vger.kernel.org, snisa.balakrishnan@gmail.com
Subject: programming using system calls
Date: Tue, 31 Jul 2007 15:53:09 +0400 [thread overview]
Message-ID: <192840a00707310453i2dde65edsdd86785bfa6b562e@mail.gmail.com> (raw)
In-Reply-To: <192840a00707310451s6a1b369eg632be924c8de1003@mail.gmail.com>
2007/7/31, nisa <snisa.balakrishnan@gmail.com>:
>
> hi,
> i am quite new to programming using system calls and would like a basic idea
> regarding the usage of system calls.
> i would like assistance in the following area of c programming in linux:
> 1.how to open a text file ,read data and print the data on console using
> system calls
> 2.create a text file and write some data
> 3.read data from a file and append that data to another file using lseek()
> 4.creation of a parent and child process using fork()
>
> --
> View this message in context: http://www.nabble.com/programming-using-system-calls-tf4192448.html#a11922382
> Sent from the linux-c-programming mailing list archive at Nabble.com.
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-c-programming" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
Well, as far as i know, man pages are a good source of knowledge.
Wait, i'll check that. Hm... Yeah, they are. :)
Everything that you are looking for is situated in the second section
of man pages.
--
Wbr, Andriy Mishkovskyy.
He's got a heart of a little child, and he keeps it in a jar on his desk.
next prev parent reply other threads:[~2007-07-31 11:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-31 11:27 programming using system calls nisa
2007-07-31 11:51 ` spiro harvey
[not found] ` <192840a00707310451s6a1b369eg632be924c8de1003@mail.gmail.com>
2007-07-31 11:53 ` Андрій Мішковський [this message]
2007-07-31 12:00 ` Mateus Interciso
2007-07-31 14:00 ` Андрій Мішковський
2007-07-31 14:13 ` Mateus Interciso
2007-08-10 14:53 ` Li YanBo
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=192840a00707310453i2dde65edsdd86785bfa6b562e@mail.gmail.com \
--to=mishok13@gmail.com \
--cc=linux-c-programming@vger.kernel.org \
--cc=snisa.balakrishnan@gmail.com \
/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).