From: "Steven Stillaway" <steve@stillaway.net>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] Re: device-mapper transition
Date: Sat Oct 12 12:30:09 2002 [thread overview]
Message-ID: <20021012172851.GB5529@sparcbox.net> (raw)
In-Reply-To: <20021011075220.GA1153@fib011235813.fsnet.co.uk>
Hello Joe,
I just noticed on your website (http://people.sistina.com/~thornber)
that you have the 2.5 DM marked as untested for Intel SMP.
I am running it on an Intel SMP box (Abit BP6 with Dual Celeron 433)
and it seems fine.
--
Steven Stillaway
steve@stillaway.ca
steve@sparcbox.net
prev parent reply other threads:[~2002-10-12 12:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1034276879.2396.11.camel@mars.goatskin.org>
2002-10-11 2:53 ` [linux-lvm] Re: device-mapper transition Joe Thornber
2002-10-11 4:05 ` Steven Stillaway
2002-10-11 4:25 ` [linux-lvm] device-mapper & proc Steven Stillaway
2002-10-11 4:48 ` Joe Thornber
2002-10-11 4:32 ` [linux-lvm] Re: device-mapper transition Joe Thornber
2002-10-11 17:09 ` Andres Salomon
2002-10-11 18:09 ` Alasdair G Kergon
2002-10-14 2:59 ` Heinz J . Mauelshagen
2002-10-12 12:30 ` Steven Stillaway [this message]
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=20021012172851.GB5529@sparcbox.net \
--to=steve@stillaway.net \
--cc=linux-lvm@sistina.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox