From: "Rafael Sisto" <rafael.sisto@gmail.com>
To: "Jan Engelhardt" <jengelh@computergmbh.de>
Cc: "Linux kernel" <linux-kernel@vger.kernel.org>
Subject: Re: new file in kernel.
Date: Sat, 19 Jan 2008 11:08:32 -0300 [thread overview]
Message-ID: <ee3dc96c0801190608q33aee0aer133611a1fc392bb4@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0801191448140.27831@fbirervta.pbzchgretzou.qr>
Dear Jan,
I had already read that webpage, but I dont need to change the data on
that file. I just want to create a new file and then close it, so I
can use it later in another system call, to mmap it to a user space.
Is it clearer now?
Can you please give me some code snippet?
Thanks again in advance and greetings!
Rafael Sisto.
(Jan, Sorry for the last mail, I answered to your personal mail only)
On Jan 19, 2008 10:49 AM, Jan Engelhardt <jengelh@computergmbh.de> wrote:
>
> On Jan 19 2008 10:42, Rafael Sisto wrote:
> >Dear forum,
> >can anybody help me with this issue?
> >
> >How do I create a new file in kernel mode?
> >I am trying to create a file in a system call I am building.
>
> http://kernelnewbies.org/FAQ/WhyWritingFilesFromKernelIsBad
>
> Even then, you are a bit too unspecific. A syscall could
> very well call a filesystem's create function and create
> a file that way, though it is a very different use-case.
>
next prev parent reply other threads:[~2008-01-19 14:08 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-19 13:42 Rafael Sisto
2008-01-19 13:48 ` Arnaldo Carvalho de Melo
2008-01-19 14:21 ` Rafael Sisto
2008-01-19 14:30 ` Jan-Benedict Glaw
2008-01-19 14:57 ` Rafael Sisto
2008-01-19 15:26 ` Stefan Richter
2008-01-19 16:15 ` Rafael Sisto
2008-01-19 16:23 ` Arnaldo Carvalho de Melo
2008-01-19 17:57 ` Stefan Richter
2008-01-19 13:49 ` Jan Engelhardt
2008-01-19 14:08 ` Rafael Sisto [this message]
2008-01-19 14:30 ` Jan Engelhardt
2008-01-19 15:12 ` Rafael Sisto
2008-01-20 1:29 ` Jan-Benedict Glaw
2008-01-21 13:00 ` Rafael Sisto
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=ee3dc96c0801190608q33aee0aer133611a1fc392bb4@mail.gmail.com \
--to=rafael.sisto@gmail.com \
--cc=jengelh@computergmbh.de \
--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®