mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Pekka Enberg <penberg@gmail.com>
To: "Guillermo López Alejos" <glalejos@gmail.com>
Cc: Linux Kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: Developing a filesystem
Date: Fri, 8 Jul 2005 13:30:12 +0300	[thread overview]
Message-ID: <84144f0205070803307548683a@mail.gmail.com> (raw)
In-Reply-To: <4fec73ca05070803144da4b3c1@mail.gmail.com>

On 7/8/05, Guillermo López Alejos <glalejos@gmail.com> wrote:
> Hi,
> 
> As I anounced a couple of weeks ago, I'm studying how to build a new
> filesystem. I have taken a look at the ramfs and also read some
> documentation about.
> 
> Now I'm writing my own dummyfs (based on ramfs) to know how this
> works, but I'm having problems compiling it; I need to include the
> "linux/fs.h" header file to have access to some structures definitions
> (such as struct file_system_type), but this is giving me some errors.
> So I think that I have to integrate my code with the kernel sources to
> make it compile.
> 
> Therefore, my question is, is there any way to check wheter my code
> compiles or not without having to integrate it with the kernel code?
> If not, is there any tutorial to learn how to integrate a filesystem
> into the Linux kernel code?

1. Example Makefile for an out-of-tree filesystem: 

http://cvs.sourceforge.net/viewcvs.py/v9fs/linux-9p/Makefile?rev=2.0&view=auto

2. Putting it into the kernel:

cat fs/ramfs/Makefile
grep -i ramfs fs/Kconfig

                              Pekka

  reply	other threads:[~2005-07-08 10:34 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-08 10:14 Guillermo López Alejos
2005-07-08 10:30 ` Pekka Enberg [this message]
2005-07-08 10:35 ` Erik Mouw

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=84144f0205070803307548683a@mail.gmail.com \
    --to=penberg@gmail.com \
    --cc=glalejos@gmail.com \
    --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®