From: peter <arevill@bigpond.net.au>
To: linux-kernel@vger.kernel.org
Subject: Steps to open a file/handled by kernel?
Date: Thu, 10 Jan 2002 04:58:05 +0800 [thread overview]
Message-ID: <3C3CAEDD.8040707@bigpond.net.au> (raw)
CC: all replies to: arevill@bigpond.net.au
Hi guys, im in discussion with one of my compsci mates to start an
intresting little project, its not concrete yet, not at all, i really
need to get a good grasp of what im going to have to code before i
decide to jump in or not, ill give you a quick run down
Basically we want to make a sort of.. auto compression/uncompression of
files as there accessed/not accessed, basically to save a hell of alot
of space, but before we even BEGIN to do it, i really need to understand
the calls and the "arguments" and the stages the kernel/userspace (if it
is invovled (if userspace is even the right word!) takes to read from a
file (and write to it while we are at it)
any information people feel is relevant or any sort of url u can point
me to or just a little guide of waht happens would be appreciiated,
please CC: all msgs to arevill@bigpond.net.au
Cheers
:)
Peter
next reply other threads:[~2002-01-09 21:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-09 20:58 peter [this message]
2002-01-09 21:09 ` Randy.Dunlap
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=3C3CAEDD.8040707@bigpond.net.au \
--to=arevill@bigpond.net.au \
--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®