X-MimeOLE: Produced By Microsoft Exchange V6.5
Received: by onstor-exch02.onstor.net 
	id <01C7A246.3E978FC9@onstor-exch02.onstor.net>; Tue, 29 May 2007 16:08:18 -0700
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Content-class: urn:content-classes:message
Subject: RE: FTP URL spec for upgrade script
Date: Tue, 29 May 2007 16:08:15 -0700
Message-ID: <BB375AF679D4A34E9CA8DFA650E2B04E03E3920B@onstor-exch02.onstor.net>
In-Reply-To: <20070529154947.2d00602d@ripper.onstor.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: FTP URL spec for upgrade script
Thread-Index: AceiQ6iF+Difvi8rSEq/ga1R9IMbIwAAlBig
From: "Eric Barrett" <eric.barrett@onstor.com>
To: "Andy Sharp" <andy.sharp@onstor.com>

Nope.  Customers who get it from our FTP site all copy-and-paste from
email, the website, or browsing, anyway.

The primary convenience is for your script not to require
username:password@... for anonymous FTP, which the current system
upgrade fails at (it actually regressed back when 1.3 came out and
hasn't been corrected).




-----Original Message-----
From: Andy Sharp=20
Sent: Tuesday, May 29, 2007 3:50 PM
To: Eric Barrett
Subject: Re: FTP URL spec for upgrade script

Well,  I'm assuming that we will have some kind of sensible shortcuts,
possibly by utilizing sym links, like

ftp://support.onstor.com/outbound/software/EverON/EverON-3.0.0.0BC.tar.g
z

where the zeroes are replaceable by version numbers.  So customers and
other people don't have to type the whole huge long thing that
contains redundant information.

On Tue, 29 May 2007 15:32:40 -0700 "Eric Barrett"
<eric.barrett@onstor.com> wrote:

> Andy,
>=20
> Well, the exact URL is going to vary, because:
>=20
> * Half of our customers use their own internal FTP servers, and half
> just download directly from us.
>=20
> * We have two public FTP sites (ftp.onstor.com, a.k.a.
> support.onstor.com, and ftp-eu.onstor.com).
>=20
> * Finally, the release will be initially posted in the 'early'
> subdirectory so the server path will change when the release becomes
> GA.
>=20
>=20
> The most common URL will be:
>=20
>
ftp://support.onstor.com/outbound/software/EverON/3.0.0.0/22xx/EverON-3.
> 0.0.0BC.tar.gz
>=20
> The release names are formulaic, i.e. EverON-$X.$Y.$Z.$W{BC,}.tar.gz.
> If "BC" doesn't exist it's Cheetah (and of course the tarball would be
> in the "44xx" subdirectory instead of "22xx").  Presumably we'll be
> using CG for Cougar, but that's for Ken et al. to decide.
>=20
>=20
>=20
> -----Original Message-----
> From: Andy Sharp=20
> Sent: Tuesday, May 29, 2007 3:19 PM
> To: Eric Barrett
> Subject: Re: FTP URL spec for upgrade script
>=20
> Thanks Eric.
>=20
> What I need to know is the exact URL that customers would have to type
> in to get the Delorean release.  The path I assume would not change
> over time, but the name of the tarball would change with each release?
>=20
> Thanks,
>=20
> a
>=20
> On Thu, 17 May 2007 13:03:53 -0700 "Eric Barrett"
> <eric.barrett@onstor.com> wrote:
>=20
> > Here's the long description:
> >=20
> > http://www.cs.tut.fi/~jkorpela/ftpurl.html
> >=20
> >=20
> > The short one is:
> >=20
> > Anonymous (login: "anonymous", password: "guest@"):
> >     ftp://HOST/path/to/file
> >=20
> > With a username/password:
> >     ftp://USER:PASSWORD@HOST/path/to/file
> >=20
> >=20
> > The path ("path/to/file" in my example) is relative.  That is, if a
> > user's homedir is /home/joe, then path/to/file is treated by every
> > browser I've ever used as /home/joe/path/to/file, probably because
> > they just do a series of relative CDs.
> >=20
> > Here's an example link from our support site:
> >=20
> >
>
ftp://support.onstor.com/outbound/software/EverON/early/2.2.2.4/22xx/Eve
> > rON-2.2.2.4BC.tar.gz
> >=20
> > Or from the internal upgrade server, which uses a username/password:
> >=20
> > ftp://upgrade:password@10.2.0.2/PATCHES/EverON-2.2.2.4BC.tar.gz=20
> >=20
> > If you want to be really spiffy, then leaving out the password
> > ("ftp://upgrade@10.2.0.2...") would make the script prompt you for
> > it, so that users don't have to enter in in plain sight, as they do
> > with the current NFXSH upgrade command.  But that's not necessary,
> > just nice-to-have.
> >=20
> > -Eric
