All of lore.kernel.org
 help / color / mirror / Atom feed
From: Oleg Drokin <green@namesys.com>
To: Moritz Angermann <moritz.angermann@gmx.net>
Cc: reiserfs-list@namesys.com
Subject: Re: O.k. so this way, r8 ?
Date: Thu, 18 Jul 2002 17:08:51 +0400	[thread overview]
Message-ID: <20020718170851.A23148@namesys.com> (raw)
In-Reply-To: <1026997025.734.8.camel@prototype>

Hello!

On Thu, Jul 18, 2002 at 02:57:05PM +0200, Moritz Angermann wrote:
> so i check it all out:
> thanks for your help.
> so this is what i'm going to do,
> i'd just like to have it confirmed, so
> i get less risk to kill my FS.

The sequence looks ok with few notes.

> #0 backing up my data
> #1 getting 2.4.18
> #2 getting all patches from
> ftp://ftp.namesys.com/pub/reiserfs-for-2.4/2.4.18.pending
> #3 applying them all to my 2.4.18 kernel.
> #4 make clean;make menuconfig;make dep;make bzfloppy[;make modules;make

You want not only have new kernel on floppy, but also as a default kernel, too.

> modules install ?]
> #5 getting
> ftp://ftp.namesys.com/pub/reiserfsprogs/reiserfsprogs-3.6.2.tar.gz
> #6 unpacking it; ./configure --prefix=/mnt/floppy/rfsp;make;make install
> #7 reboot
> #8 umount /

unmounting / is not possible, so you must boot off some rescue media here in
fact.

> #9 rfsp/reiserfsck /dev/hda6 --fix-fixable

See if it reported everything is ok or if it was recommending to do a
rebuild-tree, do the rebuild-tree too.

> #10 reboot [and hope]

Bye,
    Oleg

      reply	other threads:[~2002-07-18 13:08 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-18 12:57 O.k. so this way, r8 ? Moritz Angermann
2002-07-18 13:08 ` Oleg Drokin [this message]

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=20020718170851.A23148@namesys.com \
    --to=green@namesys.com \
    --cc=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.