From: Jan-Benedict Glaw <jbglaw@lug-owl.de>
To: linux-c-programming@vger.kernel.org
Subject: Re: Filesystem as a module?
Date: Sun, 14 Mar 2004 00:52:42 +0100 [thread overview]
Message-ID: <20040313235242.GU17857@lug-owl.de> (raw)
In-Reply-To: <20040313194721.EB5123DC2@xprdmailfe6.nwk.excite.com>
[-- Attachment #1: Type: text/plain, Size: 994 bytes --]
On Sat, 2004-03-13 14:47:21 -0500, Vineet Joglekar <vintya@excite.com>
wrote in message <20040313194721.EB5123DC2@xprdmailfe6.nwk.excite.com>:
> > Better create another directory below ./linux/fs/ and place your sources there.
>
> Thanks for the prompt reply. I'll try to do it. I have 1 more question regarding this approach. In which make files do I need to make changes / additions so that while building the kernel, my newly added directory will be compiled too?
Well, for 2.4.x, you'll need to touch ./linux/fs/Makefile,
./linux/fs/Config.in and ./linux/Documentation/Configure.help. In 2.6.x,
you need to modify ./linux/fs/Makefile and ./linux/fs/Kconfig.
MfG, JBG
--
Jan-Benedict Glaw jbglaw@lug-owl.de . +49-172-7608481
"Eine Freie Meinung in einem Freien Kopf | Gegen Zensur | Gegen Krieg
fuer einen Freien Staat voll Freier Bürger" | im Internet! | im Irak!
ret = do_actions((curr | FREE_SPEECH) & ~(NEW_COPYRIGHT_LAW | DRM | TCPA));
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-03-13 23:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-13 19:47 Filesystem as a module? Vineet Joglekar
2004-03-13 23:52 ` Jan-Benedict Glaw [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-03-12 23:02 Vineet Joglekar
2004-03-13 12:07 ` Jan-Benedict Glaw
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=20040313235242.GU17857@lug-owl.de \
--to=jbglaw@lug-owl.de \
--cc=linux-c-programming@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;
as well as URLs for NNTP newsgroup(s).