X-MimeOLE: Produced By Microsoft Exchange V6.5
Received: by onstor-exch02.onstor.net 
	id <01C73421.33F10D3C@onstor-exch02.onstor.net>; Tue, 9 Jan 2007 11:06:01 -0800
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Content-class: urn:content-classes:message
Subject: RE: No simple solution
Date: Tue, 9 Jan 2007 11:06:01 -0800
Message-ID: <BB375AF679D4A34E9CA8DFA650E2B04E0A9465@onstor-exch02.onstor.net>
In-Reply-To: <20070109101845.632e4947@ripper.onstor.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: No simple solution
thread-index: Acc0Gpm6a+6HJJFkRFqVqwkqEL5mQgABjt0g
From: "Larry Scheer" <larry.scheer@onstor.com>
To: "Andy Sharp" <andy.sharp@onstor.com>

I should have included that in my previous email. My apologies for my
thoughtlessness.
Like all of openbsd source it is kept in an obvious place ;-)

openbsd/src/usr.bin/xinstall/xinstall.c

Yea, it took me a while to find it too.

Larry



-----Original Message-----
From: Andrew Sharp [mailto:andy.sharp@onstor.com]=20
Sent: Tuesday, January 09, 2007 10:19 AM
To: Tim Gardner
Cc: Larry Scheer; Jay Michlin
Subject: Re: No simple solution

Where are we keeping the source for install?  I can't find it under
openbsd.  Or anywhere else.

a

On Mon, 8 Jan 2007 21:05:35 -0800 "Tim Gardner"
<tim.gardner@onstor.com> wrote:

> Andy,
> =20
> Please take a look at the source code for install.
> Lets find out if it is using mmap. Also look at the code for cp. We
> need to find out what is different. That will help us understand what
> is causing the corruption.=20
> Tim
> =20
>=20
> ________________________________
>=20
> From: Larry Scheer
> Sent: Mon 1/8/2007 7:32 PM
> To: Jay Michlin; Andy Sharp; Tim Gardner
> Cc: Larry Scheer
> Subject: No simple solution
>=20
>=20
>=20
> I downloaded, built, and installed the latest revision
> of /usr/bin/install from OpenBSD 4.0. I started my test suites and I
> am still seeing file corruption. (/usr/local/agile/lib/libucdmibs.so
> for instance)
>=20
> I am still seeing the corruption when running /usr/bin/install
> standalone (in a script) or with our upgrade program.
>=20
> I think this indicates it is something deep with BSD, perhaps in libc?
>=20
> I can provide a map of install so we can see all of the functions it
> uses. If that would help.
>=20
> Larry
>=20
>=20
>=20
