From: Daniel Phillips <phillips@istop.com>
To: "Kevin P. Fleming" <kpfleming@backtobasicsmgmt.com>
Cc: "Walker, Bruce J" <bruce.walker@hp.com>,
Discussion of clustering software components including GFS
<linux-cluster@redhat.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
opengfs-devel@lists.sourceforge.net,
opengfs-users@lists.sourceforge.net,
opendlm-devel@lists.sourceforge.net
Subject: Re: [Linux-cluster] Re: [ANNOUNCE] OpenSSI 1.0.0 released!!
Date: Sun, 1 Aug 2004 21:53:46 -0400 [thread overview]
Message-ID: <200408012153.46835.phillips@istop.com> (raw)
In-Reply-To: <410D2949.20503@backtobasicsmgmt.com>
On Sunday 01 August 2004 13:32, Kevin P. Fleming wrote:
> Daniel Phillips wrote:
> > On Saturday 31 July 2004 12:00, Walker, Bruce J wrote:
> >>In the 2.4 implementation, providing this one capability by
> >>leveraging devfs was quite economic, efficient and has been very stable.
> >
> > I wonder if device-mapper (slightly hacked) wouldn't be a better approach
> > for 2.6+.
>
> It appeared from the original posting that their "cluster-wide devfs"
> actually supported all types of device nodes, not just block devices. I
> don't know whether accessing a character device on another node would
> ever be useful, but certainly using device-mapper wouldn't help for that
> case.
Unless device-mapper learned how to deal with char devices...
Just a thought.
Regards,
Daniel
next prev parent reply other threads:[~2004-08-02 1:53 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-31 16:00 [Linux-cluster] Re: [ANNOUNCE] OpenSSI 1.0.0 released!! Walker, Bruce J
2004-08-01 17:30 ` Daniel Phillips
2004-08-01 17:32 ` Kevin P. Fleming
2004-08-02 1:53 ` Daniel Phillips [this message]
2004-08-02 3:13 ` Ian Kent
2004-08-16 19:26 ` Pavel Machek
2004-08-18 20:38 ` Jeff Macdonald
[not found] <2o4AV-18E-27@gated-at.bofh.it>
2004-07-31 16:54 ` Andi Kleen
2004-08-01 16:26 ` Lars Marowsky-Bree
-- strict thread matches above, loose matches on Subject: below --
2004-07-31 18:48 Walker, Bruce J
2004-08-02 0:00 Walker, Bruce J
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=200408012153.46835.phillips@istop.com \
--to=phillips@istop.com \
--cc=bruce.walker@hp.com \
--cc=kpfleming@backtobasicsmgmt.com \
--cc=linux-cluster@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=opendlm-devel@lists.sourceforge.net \
--cc=opengfs-devel@lists.sourceforge.net \
--cc=opengfs-users@lists.sourceforge.net \
/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.