All of lore.kernel.org
 help / color / mirror / Atom feed
From: Oleg Drokin <green@namesys.com>
To: Steve Pratt <slpratt@us.ibm.com>
Cc: reiserfs-list@namesys.com
Subject: Re: EVMS Reiser FSIM
Date: Tue, 4 Jun 2002 19:10:45 +0400	[thread overview]
Message-ID: <20020604191045.A10459@namesys.com> (raw)
In-Reply-To: <OFF33CCB39.8842A3DF-ON85256BCE.0050E23C@pok.ibm.com>

Hello!

On Tue, Jun 04, 2002 at 10:02:00AM -0500, Steve Pratt wrote:
 
> >What should I do to get something to appear in the disks/slices/whatever
> >lists so I can play with it?
> I need the kernel log and the Engine log (/var/log/evmsEngine.log) to be
> sure what is going on, but my first guess would be that either you did not
> select all of the right components in the kernel, or if you did that you
> might have built them as modules and not loaded them. Specifically it looks
> like the local device manager is missing.

Hm. Yes, I in fact had everything in modules.
But I have expected evms to load all the stuff its needed once evms main module
is loaded. 
It would be helpful if help entry on EVMS suggest evms might be loaded as
module, but then all of the other evms modules should be loaded by hand.

> We recommend compiling all EVMS runtime plug-in that you plan to use
> directly into your kernel.  It avoid the hassle of dealing with init
> ramdisks and lodaing modules at the right time.  If you are really set on

Since I am not planning to put my root on a EVMS volume yet, I think I can
go with modules setup, I only need to load all the modules, it seems.

> Summary: please verify that at least 'local device manager' and 'DOS
> partition manager' are built statically into the kernel, if not reconfigure
> kernel and retry.  If they are, then send me the kernel and Engine logs and
> I will see what is wrong.

Ok, thank you.  will try that.

Bye,
    Oleg

  reply	other threads:[~2002-06-04 15:10 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-04 15:02 EVMS Reiser FSIM Steve Pratt
2002-06-04 15:10 ` Oleg Drokin [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-06-04 16:45 Steve Pratt
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-31 17:03 Steve Pratt
2002-05-31 17:28 ` Oleg Drokin
2002-06-03 16:00 ` Oleg Drokin
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=20020604191045.A10459@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.