From: Leonardo Di Lella <dilella@gmx.net>
To: ssams <ssams@telkom.net>
Cc: linux-assembly@vger.kernel.org
Subject: Re: entering char from keyboard
Date: Mon, 29 Apr 2002 07:35:36 +0200 [thread overview]
Message-ID: <20020429053536.GC650@cube.free-bsd.org> (raw)
In-Reply-To: <web-7206429@m1.plasa.com>
Re!
* On 29 April, 2002 11:28:55 AM
* "ssams" (ssams@telkom.net) wrote:
> Assalamu 'alaikum..... everybody
Assalamu,
> I want to build code to enter some char from keyboard
> what syscall i need...?
#define __NR_read 3,
for reading, and maybe also __NR_write for writing it at stdout ...
look also at
$ man 2 read
Your file d. should be stdin
myst@xor:/dev$ ls -al stdin
lrwxrwxrwx 1 root root 4 24. Nov 17:38 stdin -> fd/0
bye
--
Leonardo Di Lella
[0x01] http://www.comfire.de
[0x02] http://www.netline-is.de
next prev parent reply other threads:[~2002-04-29 5:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-29 4:28 entering char from keyboard ssams
2002-04-29 5:35 ` Leonardo Di Lella [this message]
2002-04-29 10:04 ` Rudolf Marek
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=20020429053536.GC650@cube.free-bsd.org \
--to=dilella@gmx.net \
--cc=linux-assembly@vger.kernel.org \
--cc=ssams@telkom.net \
/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).