All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Masover <ninja@slaphack.com>
To: Pysiak Satriani <pysiak.satriani@wp.pl>
Cc: Reiserfs List <reiserfs-list@namesys.com>
Subject: Re: Some questions about r4
Date: Thu, 01 Sep 2005 13:43:33 -0500	[thread overview]
Message-ID: <43174BD5.1030809@slaphack.com> (raw)
In-Reply-To: <431743196ebaa@wp.pl>

Pysiak Satriani wrote:
> Hi,
> 
> Is there a r4-patch cooking for 2.6.13 ?

Maybe.  But the patches from 2.6.13-rc6-mm2 applied and ran without any 
trouble at all.  2.6.13-mm1 is out, but I haven't gotten a chance to try it.

For the record, the script to patch just reiser4 from broken-out 
mm-sources is:

cd /usr/src/linux
for patch in `egrep '^reiser4' ../broken-out/series`; do
	patch -p1 < ../broken-out/$patch || break
done

I hope this works, I haven't actually tested it against patches that 
don't apply properly (to see if the break works), and of course it 
currently breaks if patch names have spaces in them.

> Is the requirement for not enabling 4k-stacks going away soon?

Probably not.  Actually, I have no idea, but I would guess that kernel 
inclusion is more important now.

> If I patch a vanilla kernel with r4, and sop using r4, would you say that the changes I introduced by patching are rather safe to the rest of the kernel, or would you recomend going back to vanilla just in case?

Teach your mail client to wrap lines, good god!

Anyway, it would probably be a Best Practice to remove it, but I haven't 
had any stability issues using Reiser4 as my root FS for months and 
months -- has it been a year now?  I can't remember...

So, I doubt it affects the rest of the kernel.  However, I could be 
entirely wrong about this, and that could be why my sound card doesn't 
work in Quake 3 on AMD64, or why I can't get my microphone working, or 
why glxgears is so much slower with my new video card on AMD64 compared 
to my old one on an Athlon-XP.

But somehow, I doubt any of these are true.


  parent reply	other threads:[~2005-09-01 18:43 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-01 18:06 Some questions about r4 Pysiak Satriani
2005-09-01 18:19 ` Gregory Maxwell
2005-09-01 22:15   ` Hans Reiser
2005-09-01 18:43 ` David Masover [this message]
2005-09-01 20:38   ` Re[2]: " Pysiak Satriani

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=43174BD5.1030809@slaphack.com \
    --to=ninja@slaphack.com \
    --cc=pysiak.satriani@wp.pl \
    --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.