From: "Milan Holzäpfel" <lists@mjh.name>
To: reiserfs-list@namesys.com
Subject: Re: Vanilla kernel patch
Date: Fri, 8 Oct 2004 16:29:25 +0200 [thread overview]
Message-ID: <20041008162925.3e0e03c4.lists@mjh.name> (raw)
In-Reply-To: 200410071402.33421.biscani@pd.astro.it
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Thu, 7 Oct 2004 14:02:27 +0200
Francesco Biscani <biscani@pd.astro.it> wrote:
> Hi,
>
> yesterday I threw together a patchset to enable reiser4 for the vanilla
> 2.6.9-rc3 kernel. [...]
I did the same some time ago with the last official snapshot, which has
worked fine for me so far. reiser4 is used for my gentoo portage tree,
my /var filesystem, for a partition where portage compiles the packages
on and for Squid's cache (Squid is a http and ftp proxy).
> What are the pitfalls I'm falling in, doing this? Is this safe or is there
> stuff in -mm that is absolutely needed by reiser4?
Well I'd make the guess that if there is something in the mm kernel
which is absolutely needed by reiser4 then the thing won't link or you
will be unable to load the module if you chose to compile it as a
module.
> Thanks!
Regards,
Milan
- --
Milan Holzäpfel alias jagdfalke alias jag
Antworten direkt an mich Answers directly to me
gehen bitte an eine Addresse, go to an address one
die man hier finden kann: can find here, please:
Kontaktinfos sowie Contact infos as well as
Öff GnuPG-Schlüssel <URL:http://con.mjh.name/> GnuPG Public Key
GnuPG Fingerabdruck 4C8A 5FAF 5D32 6125 89D1 GnuPG Fingerprint
0CE5 DB0C AF4F 6583 7966
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
iD8DBQFBZqRF2wyvT2WDeWYRAvvvAKDjc0RjCJoA9UdcJvSk7+gtWJFJ/ACeO29S
FPoE3gdyY49VyNt/y57KLj4=
=Ms9R
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2004-10-08 14:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-07 12:02 Vanilla kernel patch Francesco Biscani
2004-10-08 14:29 ` Milan Holzäpfel [this message]
2004-10-11 9:32 ` Francesco Biscani
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=20041008162925.3e0e03c4.lists@mjh.name \
--to=lists@mjh.name \
--cc=reiserfs-list@namesys.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.