[prev in list] [next in list] [prev in thread] [next in thread]
List: veritas-vx
Subject: Re: [Veritas-vx] VSF4.1 on RHEL4 IA64
From: "Brad Boyer" <brad_boyer () symantec ! com>
Date: 2008-04-02 18:07:40
Message-ID: C365F32BBF0D1E4E9593F3DDD9C02CB3038EEAB8 () TUS1XCHCLUPIN12 ! enterprise ! veritas ! com
[Download RAW message or body]
--===============0965924846==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
boundary="----_=_NextPart_001_01C894EC.70C7E396"
This is a multi-part message in MIME format.
This issue is due to the way rpm installs i386 packages on IA64. The
package would have been built to be installed primarily on i386 systems,
but for packages where it shouldn't matter the exact same packages are
installed on compatible 64 bit systems (x86_64 and IA64) as well rather
than having native builds for all architectures. When you install an
i386 package on IA64, rpm runs inside the /emul/ia32-linux directory and
the install scripts expect to use /bin/sh from that directory. The bad
part is that rpm checks the dependencies before it changes directories,
so it thinks the native IA64 bash will satisfy the dependency and fails
during the install with misleading error messages.
I'm glad I could help you get the install working.
From: ashish madhavan [mailto:mnashish@hotmail.com]
Sent: Wednesday, April 02, 2008 12:01 AM
To: Brad Boyer; veritas-vx@mailman.eng.auburn.edu
Subject: RE: [Veritas-vx] VSF4.1 on RHEL4 IA64
Thanks Brad!!
I had all the packages you mentioned except bash-3.0-19.3.i386.rpm .
After installing this rpm my install went ahead without any issues. Is
the i386 bash so critical for veritas install? Could be cause this rpm
installed two shells
/emul/ia32-linux/bin/bash
/emul/ia32-linux/bin/sh
My issue is resolved just wanted a confirmation that VSF needs ia32
shells.
Thanks,
Ashish
________________________________
Subject: RE: [Veritas-vx] VSF4.1 on RHEL4 IA64
Date: Tue, 1 Apr 2008 11:08:13 -0700
From: brad_boyer@symantec.com
To: mnashish@hotmail.com; veritas-vx@mailman.eng.auburn.edu
Since the package that failed is an i686 package rather than a native
ia64 package, ia32el is required to run the code in this package (and
many other included packages). Without seeing the exact error, I have to
speculate on the cause. I presume you mean that you have an older
version of ia32el (version 1.1-20) installed because you don't have the
CD that contains the exact version mentioned in the document. My first
thought would be that the older version should work in most situations,
although it does have some known bugs. You should try to get the newer
version if possible, but just having the older version shouldn't cause
this error. I don't believe this particular package uses ksh, which
should make that an unlikely cause as well. If you do not have ia32el
installed at all, then that would definitely cause this error.
My next question would be if you have installed the packages from the
RHEL4 compatibility layer CD that is part of the IA64 set. This CD
includes many i686 architecture packages that are useful for running
i686 executables on your IA64 system. In particular, you would need to
have installed bash and several of the libraries from this CD. The
section of the getting started guide
(http://ftp.support.veritas.com/pub/support/products/Foundation_Suite/27
8017.pdf - page 28) after the part about installing ia32el from the
Extras CD covers this step. If you don't have these installed, then rpm
will not be able to properly install an i686 package and fails with some
errors that may look strange if you haven't seen them before. The
detailed errors from the install log would make this easier to debug,
but checking the packages you have installed is a good first step.
Here are some examples of installed native and compatibility packages on
a system I have here (you may have different versions due to updates):
$ rpm -q --queryformat '%{N}-%{V}-%{R}.%{ARCH}.rpm\n' bash
bash-3.0-19.2.i386.rpm
bash-3.0-19.2.ia64.rpm
$ rpm -q --queryformat '%{N}-%{V}-%{R}.%{ARCH}.rpm\n' glibc
glibc-2.3.4-2.ia64.rpm
glibc-2.3.4-2.9.i686.rpm
glibc-2.3.4-2.9.ia64.rpm
$ rpm -q --queryformat '%{N}-%{V}-%{R}.%{ARCH}.rpm\n' libtermcap
libtermcap-2.0.8-39.ia64.rpm
libtermcap-2.0.8-39.i386.rpm
This is on a system that I believe is running RHEL4 Update 1:
$ rpm -q redhat-release
redhat-release-4AS-2.4
If you have the i386/i686 versions of these packages, then the detailed
errors from the install logs would most likely have the information
required to debug this issue you are facing with the installer.
From: veritas-vx-bounces@mailman.eng.auburn.edu
[mailto:veritas-vx-bounces@mailman.eng.auburn.edu] On Behalf Of ashish
madhavan
Sent: Tuesday, April 01, 2008 4:03 AM
To: veritas-vx@mailman.eng.auburn.edu
Subject: [Veritas-vx] VSF4.1 on RHEL4 IA64
Hi,
I am not able to proceed with the install of Veritas SF 4.1 install on
RHEL IA64. It errors out with:
# ./installsf
:::
CPI WARNING V-9-0-0 Could not add VRTScpi-4.1.0.151-GENERIC.i686
.rpm rpm to linbgb123
The "Getting Started Guide" says I have to install rpms
ia32el-1.2-3.ia64.rpm & ksh-20040229-12.ia64.rpm from RHEL4 IA64 (Red
Hat Enterprise Linux Extras) CD. I am not having that CD hence was able
to get ia32el-1.1-20.
Could these rpms be the reson that VRTScpi isn't installing?
Thanks,
Ashish
________________________________
Exclusive Marriage Proposals! Find UR life partner at Shaadi.com Try it!
<http://ss1.richmedia.in/recurl.asp?pid=430>
________________________________
Planning marriage in 2008! Join Shaadi.com matrimony FREE! Try it now!
<http://ss1.richmedia.in/recurl.asp?pid=429>
[Attachment #3 (text/html)]
<html xmlns:v="urn:schemas-microsoft-com:vml" \
xmlns:o="urn:schemas-microsoft-com:office:office" \
xmlns:w="urn:schemas-microsoft-com:office:word" \
xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" \
xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=Content-Type content="text/html; charset=us-ascii">
<meta name=Generator content="Microsoft Word 12 (filtered medium)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]-->
<style>
<!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
p.ecmsonormal, li.ecmsonormal, div.ecmsonormal
{mso-style-name:ec_msonormal;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
p.ecmsochpdefault, li.ecmsochpdefault, div.ecmsochpdefault
{mso-style-name:ec_msochpdefault;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
span.ecmsohyperlink
{mso-style-name:ec_msohyperlink;}
span.ecmsohyperlinkfollowed
{mso-style-name:ec_msohyperlinkfollowed;}
span.ecemailstyle18
{mso-style-name:ec_emailstyle18;}
p.ecmsonormal1, li.ecmsonormal1, div.ecmsonormal1
{mso-style-name:ec_msonormal1;
mso-margin-top-alt:auto;
margin-right:0in;
margin-bottom:0in;
margin-left:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
span.ecmsohyperlink1
{mso-style-name:ec_msohyperlink1;
color:blue;
text-decoration:underline;}
span.ecmsohyperlinkfollowed1
{mso-style-name:ec_msohyperlinkfollowed1;
color:purple;
text-decoration:underline;}
span.ecemailstyle181
{mso-style-name:ec_emailstyle181;
font-family:"Calibri","sans-serif";
color:#1F497D;}
p.ecmsochpdefault1, li.ecmsochpdefault1, div.ecmsochpdefault1
{mso-style-name:ec_msochpdefault1;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:10.0pt;
font-family:"Times New Roman","serif";}
span.EmailStyle28
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page Section1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
{page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=EN-US link=blue vlink=purple>
<div class=Section1>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>This issue is due to the way rpm installs i386 packages on IA64.
The package would have been built to be installed primarily on i386 systems,
but for packages where it shouldn’t matter the exact same packages are
installed on compatible 64 bit systems (x86_64 and IA64) as well rather than
having native builds for all architectures. When you install an i386 package on
IA64, rpm runs inside the /emul/ia32-linux directory and the install scripts expect
to use /bin/sh from that directory. The bad part is that rpm checks the
dependencies before it changes directories, so it thinks the native IA64 bash
will satisfy the dependency and fails during the install with misleading error
messages.<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'> <o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>I’m glad I could help you get the install \
working.<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<div>
<div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'>
<p class=MsoNormal><b><span \
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span \
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> ashish madhavan \
[mailto:mnashish@hotmail.com] <br> <b>Sent:</b> Wednesday, April 02, 2008 12:01 \
AM<br> <b>To:</b> Brad Boyer; veritas-vx@mailman.eng.auburn.edu<br>
<b>Subject:</b> RE: [Veritas-vx] VSF4.1 on RHEL4 IA64<o:p></o:p></span></p>
</div>
</div>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal style='margin-bottom:12.0pt'><span style='font-size:10.0pt;
font-family:"Tahoma","sans-serif"'><br>
Thanks Brad!!<br>
I had all the packages you mentioned except bash-3.0-19.3.i386.rpm .
After installing this rpm my install went ahead without any issues. Is the i386
bash so critical for veritas install? Could be cause this rpm installed
two shells<br>
/emul/ia32-linux/bin/bash<br>
/emul/ia32-linux/bin/sh<br>
<br>
My issue is resolved just wanted a confirmation that VSF needs ia32 shells.<br>
<br>
Thanks,<br>
Ashish<br>
<br>
<br>
<o:p></o:p></span></p>
<div class=MsoNormal align=center style='text-align:center'><span
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>
<hr size=2 width="100%" align=center>
</span></div>
<p class=MsoNormal style='margin-bottom:12.0pt'><span style='font-size:10.0pt;
font-family:"Tahoma","sans-serif"'>Subject: RE: [Veritas-vx] VSF4.1 on RHEL4
IA64<br>
Date: Tue, 1 Apr 2008 11:08:13 -0700<br>
From: brad_boyer@symantec.com<br>
To: mnashish@hotmail.com; veritas-vx@mailman.eng.auburn.edu<o:p></o:p></span></p>
<div>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Since the package that failed is an i686 package rather than a
native ia64 package, ia32el is required to run the code in this package (and
many other included packages). Without seeing the exact error, I have to
speculate on the cause. I presume you mean that you have an older version of
ia32el (version 1.1-20) installed because you don’t have the CD that
contains the exact version mentioned in the document. My first thought would be
that the older version should work in most situations, although it does have
some known bugs. You should try to get the newer version if possible, but just
having the older version shouldn’t cause this error. I don’t
believe this particular package uses ksh, which should make that an unlikely
cause as well. If you do not have ia32el installed at all, then that would definitely
cause this error.</span><span \
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'><o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'> </span><span \
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'><o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>My next question would be if you have installed the packages
from the RHEL4 compatibility layer CD that is part of the IA64 set. This CD
includes many i686 architecture packages that are useful for running i686
executables on your IA64 system. In particular, you would need to have
installed bash and several of the libraries from this CD. The section of the
getting started guide (<a
href="http://ftp.support.veritas.com/pub/support/products/Foundation_Suite/278017.pdf"
target="_blank">http://ftp.support.veritas.com/pub/support/products/Foundation_Suite/278017.pdf</a>
- page 28) after the part about installing ia32el from the Extras CD covers
this step. If you don’t have these installed, then rpm will not be able
to properly install an i686 package and fails with some errors that may look
strange if you haven’t seen them before. The detailed errors from the
install log would make this easier to debug, but checking the packages you have
installed is a good first step.</span><span style='font-size:10.0pt;font-family:
"Tahoma","sans-serif"'><o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'> </span><span \
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'><o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Here are some examples of installed native and compatibility
packages on a system I have here (you may have different versions due to
updates):</span><span \
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'><o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'> </span><span \
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'><o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>$ rpm -q --queryformat '%{N}-%{V}-%{R}.%{ARCH}.rpm\n' bash</span><span
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'><o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>bash-3.0-19.2.i386.rpm</span><span style='font-size:10.0pt;
font-family:"Tahoma","sans-serif"'><o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>bash-3.0-19.2.ia64.rpm</span><span style='font-size:10.0pt;
font-family:"Tahoma","sans-serif"'><o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>$ rpm -q --queryformat '%{N}-%{V}-%{R}.%{ARCH}.rpm\n' \
glibc</span><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'><o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>glibc-2.3.4-2.ia64.rpm</span><span style='font-size:10.0pt;
font-family:"Tahoma","sans-serif"'><o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>glibc-2.3.4-2.9.i686.rpm</span><span style='font-size:10.0pt;
font-family:"Tahoma","sans-serif"'><o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>glibc-2.3.4-2.9.ia64.rpm</span><span style='font-size:10.0pt;
font-family:"Tahoma","sans-serif"'><o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>$ rpm -q --queryformat '%{N}-%{V}-%{R}.%{ARCH}.rpm\n' \
libtermcap</span><span \
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'><o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>libtermcap-2.0.8-39.ia64.rpm</span><span style='font-size:10.0pt;
font-family:"Tahoma","sans-serif"'><o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>libtermcap-2.0.8-39.i386.rpm</span><span style='font-size:10.0pt;
font-family:"Tahoma","sans-serif"'><o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'> </span><span \
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'><o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>This is on a system that I believe is running RHEL4 Update \
1:</span><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'><o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'> </span><span \
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'><o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>$ rpm -q redhat-release</span><span style='font-size:10.0pt;
font-family:"Tahoma","sans-serif"'><o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>redhat-release-4AS-2.4</span><span style='font-size:10.0pt;
font-family:"Tahoma","sans-serif"'><o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'> </span><span \
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'><o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>If you have the i386/i686 versions of these packages, then the
detailed errors from the install logs would most likely have the information
required to debug this issue you are facing with the installer.</span><span
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'><o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'> </span><span \
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'><o:p></o:p></span></p>
<div>
<div style='border:none;border-top:solid windowtext 1.0pt;padding:3.0pt 0in 0in 0in;
border-color:-moz-use-text-color -moz-use-text-color'>
<p class=MsoNormal><b><span \
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span \
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> \
veritas-vx-bounces@mailman.eng.auburn.edu \
[mailto:veritas-vx-bounces@mailman.eng.auburn.edu] <b>On Behalf Of </b>ashish \
madhavan<br> <b>Sent:</b> Tuesday, April 01, 2008 4:03 AM<br>
<b>To:</b> veritas-vx@mailman.eng.auburn.edu<br>
<b>Subject:</b> [Veritas-vx] VSF4.1 on RHEL4 IA64<o:p></o:p></span></p>
</div>
</div>
<p class=MsoNormal><span \
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> <o:p></o:p></span></p>
<p class=MsoNormal><span \
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'><br> Hi,<br>
I am not able to proceed with the install of Veritas SF 4.1 install on
RHEL IA64. It errors out with:<br>
<br>
# ./installsf<br>
> > > <br>
CPI WARNING V-9-0-0 Could not add \
VRTScpi-4.1.0.151-GENERIC.i686<o:p></o:p></span></p>
<div id="EC_1hfq">
<p class=MsoNormal><span \
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>.rpm rpm to linbgb123<br>
<br>
The "Getting Started Guide" says I have to install rpms
ia32el-1.2-3.ia64.rpm & ksh-20040229-12.ia64.rpm from RHEL4 IA64 (Red Hat
Enterprise Linux Extras) CD. I am not having that CD hence was able to get
ia32el-1.1-20.<br>
<br>
Could these rpms be the reson that VRTScpi isn't installing?<br>
<br>
Thanks,<br>
Ashish<o:p></o:p></span></p>
</div>
<p class=MsoNormal style='margin-bottom:12.0pt'><span style='font-size:10.0pt;
font-family:"Tahoma","sans-serif"'><br>
<br>
<o:p></o:p></span></p>
<div class=MsoNormal align=center style='text-align:center'><span
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>
<hr size=2 width="100%" align=center>
</span></div>
<p class=MsoNormal><span \
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>Exclusive Marriage \
Proposals! Find UR life partner at Shaadi.com <a \
href="http://ss1.richmedia.in/recurl.asp?pid=430" target="_blank">Try \
it!</a><o:p></o:p></span></p>
</div>
<p class=MsoNormal><span \
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'><o:p> </o:p></span></p>
<div class=MsoNormal align=center style='text-align:center'><span
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>
<hr size=2 width="100%" align=center>
</span></div>
<p class=MsoNormal><span \
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>Planning marriage in 2008! \
Join Shaadi.com matrimony FREE! <a href="http://ss1.richmedia.in/recurl.asp?pid=429" \
target="_new">Try it now!</a><o:p></o:p></span></p>
</div>
</body>
</html>
_______________________________________________
Veritas-vx maillist - Veritas-vx@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-vx
--===============0965924846==--
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic