public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Chris Mason <mason@suse.com>
To: Hans Reiser <reiser@namesys.com>,
	Ryan Cumming <bodnar42@phalynx.dhs.org>
Cc: linux-kernel@vger.kernel.org, stewart@neuron.com,
	edward@thebsh.namesys.com
Subject: Re: passing params to boot readonly
Date: Thu, 13 Dec 2001 15:07:34 -0500	[thread overview]
Message-ID: <3372290000.1008274053@tiny> (raw)
In-Reply-To: <3C18FB3D.7060206@namesys.com>
In-Reply-To: <3C1841BB.8010003@neuron.com> <E16EPYW-0003nW-00@phalynx> <3C1874D5.5050205@namesys.com> <E16EYh6-0004At-00@phalynx> <3C18FB3D.7060206@namesys.com>



On Thursday, December 13, 2001 10:02:21 PM +0300 Hans Reiser
<reiser@namesys.com> wrote:

> Ryan Cumming wrote:
> 
>> On December 13, 2001 01:28, Hans Reiser wrote:
>> 
>>>> It'd probably be pretty easy to make a boot disk using a hacked version
>>>> of ReiserFS that refuses to replay the journal, by adding a "return 0;"
>>>> near the top of journal_read(struct super_block *) in journal.c.
>>>> However, you might feel more comfortable sending it off for data
>>>> recovery than testing kernel hacks on it ;)
>>>> 
>> 
>>> why not just edit the source code directly and recompile?

I posted a path for this a few months ago, hold on I'm rediffing real quick...

-chris


  reply	other threads:[~2001-12-13 20:12 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-13  5:50 passing params to boot readonly Stewart Allen
2001-12-13  6:41 ` Ryan Cumming
2001-12-13  9:28   ` Hans Reiser
2001-12-13 15:52     ` stewart
2001-12-13 16:26     ` Ryan Cumming
2001-12-13 19:02       ` Hans Reiser
2001-12-13 20:07         ` Chris Mason [this message]
2001-12-13 20:49           ` Chris Mason
2001-12-13 15:01   ` Jesse Pollard
2001-12-13 15:56     ` stewart

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=3372290000.1008274053@tiny \
    --to=mason@suse.com \
    --cc=bodnar42@phalynx.dhs.org \
    --cc=edward@thebsh.namesys.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=reiser@namesys.com \
    --cc=stewart@neuron.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox