From: "P.Agenbag" <internet@mweb.co.za>
To: linux-kernel <linux-kernel@vger.kernel.org>
Subject: ext3 and reiserfs / patches
Date: Tue, 30 Oct 2001 20:49:15 +0200 [thread overview]
Message-ID: <3BDEF62B.5050600@mweb.co.za> (raw)
Hmm, very stupid question...
Firstly, thanks to all the responses helping me to get the
(EXPERIMENTAL) out of the way...
Now, is reiserfs the same as ext3? if not, what's the diff/best?
Also, concerning the patches
I only once attempted to patch a kernel and it came out a beeeeeg
messup. I'm not very sure about the procedure, I always untar my new
kernel in /opt and then rename the linux folder to the version number (
sometimes have 4 or 5 kernels, so need to distinguish...)
Lets say I have a /opt/247 kernel source , how exactly would I patch it
and with which of the patches? Do you patch the 247 kernel with the 247
patch, or do you patch it with a higher version, and if so, how many
"steps" can you go higher?
Sorry for the ignorance, but hey, atleast i'm willing to learn!
Thanks
next reply other threads:[~2001-10-30 19:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-30 18:49 P.Agenbag [this message]
2001-10-31 1:15 ` ext3 and reiserfs / patches Mike Fedyk
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=3BDEF62B.5050600@mweb.co.za \
--to=internet@mweb.co.za \
--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