From: Joe Feise <jfeise@feise.com>
To: "Vladimir V. Saveliev" <vs@namesys.com>
Cc: reiserfs-list@namesys.com
Subject: Re: Read errors from r/o-mounted reiser4
Date: Wed, 18 Jan 2006 08:33:15 -0800 [thread overview]
Message-ID: <43CE6DCB.7090506@feise.com> (raw)
In-Reply-To: <1137632415.6573.4.camel@tribesman.namesys.com>
Vladimir V. Saveliev wrote on 01/18/06 17:00:
> Hello
>
> On Tue, 2006-01-17 at 08:56 -0800, Joe Feise wrote:
>> unfortunately, the patch did not help. I still get the same errors:
>>
> sorry, please try new version of patch. (you have to patch -R the old
> one).
Vladimir,
thanks. This patch works.
$: mount -o ro,remount /usr
$: make xconfig
CHECK qt
HOSTCC scripts/kconfig/kconfig_load.o
/usr/lib/qt/bin/moc -i scripts/kconfig/qconf.h -o scripts/kconfig/qconf.moc
HOSTCXX scripts/kconfig/qconf.o
HOSTLD scripts/kconfig/qconf
...
-Joe
next prev parent reply other threads:[~2006-01-18 16:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-28 5:25 Read errors from r/o-mounted reiser4 Joe Feise
2005-12-29 2:31 ` Vladimir V. Saveliev
2006-01-02 9:04 ` Joe Feise
2006-01-18 0:08 ` Vladimir V. Saveliev
2006-01-17 16:56 ` Joe Feise
2006-01-19 1:00 ` Vladimir V. Saveliev
2006-01-18 16:33 ` Joe Feise [this message]
2006-01-17 19:06 ` Hans Reiser
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=43CE6DCB.7090506@feise.com \
--to=jfeise@feise.com \
--cc=reiserfs-list@namesys.com \
--cc=vs@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.