From: Robert Hancock <hancockr@shaw.ca>
To: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: returning text from a system call
Date: Tue, 22 Jun 2004 20:49:50 -0600 [thread overview]
Message-ID: <013901c458cc$c14b0b70$6401a8c0@northbrook> (raw)
In-Reply-To: <fa.ln13q27.174i3bp@ifi.uio.no>
I'm guessing this is an exercise or something - I'm not sure exactly what
you're trying to accomplish with this - but if you created a new system
call, all you'd likely need to do is to have the caller pass in a pointer to
a buffer, as well as the buffer size, with the system call, then just copy
the data into/out of the buffer using copy_to_user and copy_from_user.
----- Original Message -----
From: "so usp" <so_usp@yahoo.com.br>
Newsgroups: fa.linux.kernel
To: <linux-kernel@vger.kernel.org>
Sent: Monday, June 21, 2004 2:28 PM
Subject: returning text from a system call
> Hi,
>
> I'm implementing a system call, and I want to return
> information (text data) to the user without using the
> /var/log/messages (using the printk function). I've
> been thinking about writing in a file, but I really
> don't know how to manipulate files in kernel mode. The
> text could be returned to the command line as well,
> but I either don't know how to do that. Does anybody
> could help me how to return text (both ways would be
> good) from a system call?
>
> Thanks, and sorry for the English.
> so_usp
>
> ______________________________________________________________________
>
> Yahoo! Mail - agora com 100MB de espaço, anti-spam e antivírus grá=
> tis!
> http://br.info.mail.yahoo.com/
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel"=
> in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
next parent reply other threads:[~2004-06-23 2:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fa.ln13q27.174i3bp@ifi.uio.no>
2004-06-23 2:49 ` Robert Hancock [this message]
2004-06-21 20:27 so usp
2004-06-22 8:50 ` Helge Hafting
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='013901c458cc$c14b0b70$6401a8c0@northbrook' \
--to=hancockr@shaw.ca \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®