From: Paul P Komkoff Jr <i@stingr.net>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.6-rc2-bk3 (and earlier?) mount problem (?
Date: Tue, 27 Apr 2004 18:05:34 +0400 [thread overview]
Message-ID: <20040427140533.GI14129@stingr.net> (raw)
In-Reply-To: <Pine.LNX.4.58.0404271500210.27538@alpha.polcom.net>
Replying to Grzegorz Kulewski:
> But it is strange that I need kernel patch even if I have no evms
> or dm volumes in my system. Can not it be solved in mainstream kernels?
> Maybe there should be warning in config help temporaily? Maybe even note
> after option name?
This defect grew up off a disagreement between bdclaim authors and
evms authors, but as gentoo is topmost in this pyramid I consider it's
guilty :)
just exclude yours partitioned drivers out of evms scan
(/etc/evms.conf)
-or-
mount it thru evms nodes (/dev/evms/*)
--
Paul P 'Stingray' Komkoff Jr // http://stingr.net/key <- my pgp key
This message represents the official view of the voices in my head
next prev parent reply other threads:[~2004-04-27 14:05 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-26 8:39 2.6.6-rc2-mm2 Andrew Morton
2004-04-26 16:55 ` 2.6.6-rc2-mm2 Zwane Mwaikambo
2004-04-26 17:11 ` 2.6.6-rc2-mm2 raven
2004-04-26 17:37 ` 2.6.6-rc2-bk3 (and earlier?) mount problem (?) Grzegorz Kulewski
2004-04-26 18:08 ` Linus Torvalds
2004-04-26 22:08 ` Grzegorz Kulewski
2004-04-26 22:13 ` Linus Torvalds
2004-04-26 22:38 ` Grzegorz Kulewski
2004-04-26 22:56 ` viro
2004-04-27 0:04 ` Grzegorz Kulewski
2004-04-27 0:23 ` viro
2004-04-27 0:43 ` viro
2004-04-27 1:00 ` Linus Torvalds
2004-04-27 1:07 ` 2.6.6-rc2-bk3 (and earlier?) mount problem (? viro
2004-04-27 9:12 ` Grzegorz Kulewski
2004-04-27 12:51 ` Chris Mason
2004-04-27 13:07 ` Grzegorz Kulewski
2004-04-27 14:05 ` Paul P Komkoff Jr [this message]
2004-04-27 18:34 ` viro
2004-04-27 20:04 ` Paul P Komkoff Jr
2004-04-27 20:28 ` viro
2004-04-27 20:39 ` Grzegorz Kulewski
2004-04-27 21:35 ` viro
2004-04-27 21:59 ` Grzegorz Kulewski
2004-04-28 10:19 ` Paul P Komkoff Jr
2004-06-19 16:59 ` Memory and rsync problem with vanilla 2.6.7 Grzegorz Kulewski
2004-06-19 17:50 ` Linus Torvalds
2004-06-20 3:47 ` Nick Piggin
2004-06-20 14:18 ` Grzegorz Kulewski
2004-06-20 14:41 ` Grzegorz Kulewski
2004-06-20 14:45 ` Nick Piggin
2004-06-20 20:34 ` Grzegorz Kulewski
2004-06-21 16:22 ` Grzegorz Kulewski
2004-06-20 13:24 ` Grzegorz Kulewski
2004-06-20 14:04 ` Sam Ravnborg
2004-06-21 18:36 ` network related(?) kernel panic (2.6.7-bk4) Grzegorz Kulewski
2004-04-26 18:52 ` 2.6.6-rc2-mm2 Frédéric L. W. Meunier
2004-04-26 23:06 ` 2.6.6-rc2-mm2 (compile stats) John Cherry
2004-04-28 9:37 ` 2.6.6-rc2-mm2 William Lee Irwin III
2004-04-29 18:41 ` 2.6.6-rc2-mm2 William Lee Irwin III
2004-04-29 20:45 ` 2.6.6-rc2-mm2 Andrew Morton
2004-04-29 21:18 ` 2.6.6-rc2-mm2 William Lee Irwin III
2004-04-30 0:24 ` 2.6.6-rc2-mm2 William Lee Irwin III
2004-04-30 2:05 ` 2.6.6-rc2-mm2 James Bottomley
2004-04-30 2:24 ` 2.6.6-rc2-mm2 William Lee Irwin III
-- strict thread matches above, loose matches on Subject: below --
2004-04-28 7:52 2.6.6-rc2-bk3 (and earlier?) mount problem (? Henning Rohde
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=20040427140533.GI14129@stingr.net \
--to=i@stingr.net \
--cc=linux-kernel@vger.kernel.org \
/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