From: Oleg Drokin <green@namesys.com>
To: Steve Pratt <slpratt@us.ibm.com>
Cc: reiserfs-list@namesys.com
Subject: Re: EVMS Reiser FSIM
Date: Mon, 3 Jun 2002 20:00:45 +0400 [thread overview]
Message-ID: <20020603200045.A6087@namesys.com> (raw)
In-Reply-To: <OFAADA662B.00161B0E-ON85256BCA.005CD105@pok.ibm.com>
Hello!
On Fri, May 31, 2002 at 12:03:18PM -0500, Steve Pratt wrote:
I've spent some time today trying to get current EVMS version to run and see
what is it (live) but failed miserably.
2.4.18 kernel files for 2.4.18 cannot be compiled at all and are horribly
broken in some ways.
2.5.11 kernel files can be compiled with 2.5.11, but then evmsgui complained
that while kernel's ioctl is version 11, evms gui is expecting ioctl version 10.
Any advices on how can outside man look into current state of things on evms
without waiting for new release for several weeks?
Thank you.
Bye,
Oleg
next prev parent reply other threads:[~2002-06-03 16:00 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-31 17:03 EVMS Reiser FSIM Steve Pratt
2002-05-31 17:28 ` Oleg Drokin
2002-06-03 16:00 ` Oleg Drokin [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-06-04 16:45 Steve Pratt
2002-06-04 15:02 Steve Pratt
2002-06-04 15:10 ` Oleg Drokin
2002-06-03 23:34 Steve Pratt
2002-06-03 21:03 Steve Pratt
2002-06-04 6:09 ` Oleg Drokin
2002-06-03 19:04 Steve Pratt
2002-06-03 19:36 ` Oleg Drokin
2002-05-31 17:40 Steve Pratt
2002-06-01 1:35 ` Andrew Clausen
2002-05-30 19:02 Steve Pratt
2002-05-31 13:43 ` Andrew Clausen
2002-05-30 17:14 Steve Pratt
2002-05-31 9:26 ` Oleg Drokin
2002-05-29 16:28 Steve Pratt
2002-05-30 7:37 ` Yury Umanets
2002-05-30 9:53 ` Andrew Clausen
2002-05-30 12:56 ` Hans Reiser
2002-05-30 23:50 ` Andrew Clausen
2002-05-29 13:46 Steve Pratt
2002-05-29 14:17 ` Yury Umanets
2002-05-30 5:09 ` Oleg Drokin
2002-05-30 5:32 ` Adrian Phillips
2002-05-30 5:54 ` Oleg Drokin
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=20020603200045.A6087@namesys.com \
--to=green@namesys.com \
--cc=reiserfs-list@namesys.com \
--cc=slpratt@us.ibm.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.