From: Moritz Angermann <moritz.angermann@gmx.net>
To: reiserfs-list@namesys.com
Subject: problems with patching.
Date: 18 Jul 2002 15:52:42 +0200 [thread overview]
Message-ID: <1027000362.734.14.camel@prototype> (raw)
o.k. i tryed to patch my 2.4.18 kernel with the patches from
ftp://ftp.namesys.com/pub/reiserfs-for-2.4/2.4.18.pending
as sugested...
but a few of them fail to work.
for a few i had to link /usr/src/linux to /usr/src/linux-2.4.18 and to
/usr/src/linux-2.4.18.o
a few were trying to patch 2.4.9-pre* .. or s.th.
one was trying to patch 'a' and one was trying to patch a SuSE kernel.
erm guys. this is no way user friendly ...
and really confusing.
i just wonder if i now made my kernel more safe or if i broke it...
i'll now do a recompiling, but first switching on ramdisk support,
than rebootig and running mkrescue, on my debian box. as the debian ppl
told me in #debian on OPN.
i'll put the reiserfs tools on my secound partition. so i can have /
unmounted and still have access to the reiserfsprogs.
so any final sugestions ?#
thanks,
-moritz
next reply other threads:[~2002-07-18 13:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-18 13:52 Moritz Angermann [this message]
2002-07-18 14:06 ` problems with patching Kuba Ober
2002-07-18 14:47 ` Philippe Gramoullé
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=1027000362.734.14.camel@prototype \
--to=moritz.angermann@gmx.net \
--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.