AF:
NF:0
PS:10
SRH:1
SFN:
DSR:
MID:<20080428132736.29c81d0d@ripper.onstor.net>
CFG:
PT:0
S:andy.sharp@onstor.com
RQ:
SSV:onstor-exch02.onstor.net
NSV:
SSH:
R:<glyn.bowden@onstor.com>,<eric.barrett@onstor.com>,<narayan.venkat@onstor.com>,<larry.scheer@onstor.com>,<neil.neben@onstor.com>,<doug.cook@onstor.com>,<tim.gardner@onstor.com>,<rich.lareau@onstor.com>,<dl-cstech@onstor.com>
MAID:1
X-Sylpheed-Privacy-System:
X-Sylpheed-Sign:0
SCF:#mh/Mailbox/sent
RMID:#imap/andys@onstor.net@onstor-exch02.onstor.net/INBOX	0	BB375AF679D4A34E9CA8DFA650E2B04E083CD222@onstor-exch02.onstor.net
X-Sylpheed-End-Special-Headers: 1
Date: Mon, 28 Apr 2008 13:28:52 -0700
From: Andrew Sharp <andy.sharp@onstor.com>
To: "Glyn Bowden" <glyn.bowden@onstor.com>
Cc: "Eric Barrett" <eric.barrett@onstor.com>, "Narayan Venkat"
 <narayan.venkat@onstor.com>, "Larry Scheer" <larry.scheer@onstor.com>,
 "Neil Neben" <neil.neben@onstor.com>, "Doug Cook" <doug.cook@onstor.com>,
 "Tim Gardner" <tim.gardner@onstor.com>, "Rich LaReau"
 <rich.lareau@onstor.com>, "dl-cstech" <dl-cstech@onstor.com>
Subject: Re: Help! with upgrade
Message-ID: <20080428132852.45028510@ripper.onstor.net>
In-Reply-To: <BB375AF679D4A34E9CA8DFA650E2B04E083CD222@onstor-exch02.onstor.net>
References: <BB375AF679D4A34E9CA8DFA650E2B04E083CD222@onstor-exch02.onstor.net>
Organization: Onstor
X-Mailer: Sylpheed-Claws 2.6.0 (GTK+ 2.8.20; x86_64-pc-linux-gnu)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

The ftp command on OpenBSD currently does some of that:

http://www.openbsd.org/cgi-bin/man.cgi?query=ftp&apropos=0&sektion=0&manpath=OpenBSD+2.8&arch=i386&format=html

On Mon, 28 Apr 2008 11:31:27 -0700 "Glyn Bowden"
<glyn.bowden@onstor.com> wrote:

> Would be nicer to have protocol independance so the url could
> determine then such as ftp tftp scp http etc etc like the cisco
> switches do. This would be far simpler for secure sites to maintain
> their own repositories without having to set up explicit services
> they normally wouldn't require. Or dare I suggest using nfs or cifs
> to copy the image to the management vol and install from there? ;)
> 
> Glyn
> --------------------------
> Sent using BlackBerry
> 
> 
> -----Original Message-----
> From: Eric Barrett
> To: Narayan Venkat; Andy Sharp
> CC: Larry Scheer; Neil Neben; Doug Cook; Tim Gardner; Rich LaReau;
> dl-cstech Sent: Mon Apr 28 10:49:22 2008
> Subject: RE: Help! with upgrade
> 
> Actually, it looks like our FTP client does default to binary now.
> (Maybe it always did and I'm just confused.)  So this case must have
> been because the customer used the Windows FTP client. 
> 
> -----Original Message-----
> From: Eric Barrett 
> Sent: Monday, April 28, 2008 10:43 AM
> To: Narayan Venkat; Andy Sharp
> Cc: Larry Scheer; Neil Neben; Doug Cook; Tim Gardner; Rich LaReau;
> dl-cstech Subject: RE: Help! with upgrade
> 
> I've been arguing this for years :)  That doesn't mean we shouldn't
> fix the FTP client. 
> 
> -----Original Message-----
> From: Narayan Venkat 
> Sent: Monday, April 28, 2008 10:41 AM
> To: Andy Sharp; Eric Barrett
> Cc: Larry Scheer; Neil Neben; Doug Cook; Tim Gardner; Rich LaReau;
> dl-cstech Subject: RE: Help! with upgrade
> 
> Thumbs up to using HTTP.
> 
> Narayan Venkat
> Vice President, Marketing
> ONStor Inc. (www.onstor.com)
> Tel: (408) 963-2404
> Cell: (408) 221-4297
> -----Original Message-----
> From: Andy Sharp 
> Sent: Monday, April 28, 2008 9:25 AM
> To: Eric Barrett
> Cc: Larry Scheer; Neil Neben; Doug Cook; Tim Gardner; Rich LaReau;
> dl-cstech Subject: Re: Help! with upgrade
> 
> Just to repeat, we should switch our practice to use http to download
> rather than ftp.  FTP is a dinosaur, and this is just one of the
> many reasons.
> 
> Cheers,
> 
> a
> 
> On Mon, 28 Apr 2008 09:12:14 -0700 "Eric Barrett"
> <eric.barrett@onstor.com> wrote:
> 
> > Almost all FTP clients now default to binary.  Ours (on BSD) is old
> > and defaults to ASCII, as does the Windows CLI FTP client.
> > 
> > I suspect it would be very simple to change our default in the
> > source -- I'll look into it.
> > 
> > 
> > -----Original Message-----
> > From: Larry Scheer 
> > Sent: Sunday, April 27, 2008 6:16 PM
> > To: Neil Neben; Doug Cook; Tim Gardner; Rich LaReau; dl-cstech
> > Subject: RE: Help! with upgrade
> > 
> > When using FTP to donwload/upload the script use binary mode and not
> > ASCII. Yhis will prevent the conversion of the file from UNIX format
> > to a DOS format.
> > 
> > Larry
> > 
> > -----Original Message-----
> > From: Neil Neben
> > Sent: Sat 4/26/2008 7:52 AM
> > To: Doug Cook; Tim Gardner; Rich LaReau; dl-cstech
> > Subject: Re: Help! with upgrade
> >  
> > I can discuss / add this process to my module where I thoroughly
> > discuss our upgrades. Or at the very least indicate what would be a
> > best practice for downloads.
> > Sent from my Blackberry Wireless Device - Please ignore the typo's 
> > 
> > Regard's
> > 
> > -Neil
> > 
> > -----Original Message-----
> > From: Doug Cook
> > To: Tim Gardner; Rich LaReau; dl-cstech
> > Sent: Sat Apr 26 05:29:30 2008
> > Subject: RE: Help! with upgrade
> > 
> > 
> > Hey Tim,
> > 
> > You are correct, and I have seen this issue many, many times.  It
> > revolves around how the file is downloaded from the FTP server.
> > Some clients, in text versus binary mode, will append a carriage
> > return at the end of each line, hence the control-M at the end of
> > each line.  I see this almost every time when, as root on the
> > filer, I pull down the install script from an ftp server.  In fact,
> > I open the install script on the filer every time I use one and
> > verify there are no appended control characters.
> > 
> > Folks, there is no need to panic when you see this as it is
> > ultra-easy to remedy.  Once you download the install script to the
> > filer, open it in vi.  If you see the control-M's at the end of
> > each line you can do the following:
> > 
> > In command mode in vi enter the following command:
> > 
> > :%s/<ctrl>-v<ctrl>-m//g
> > 
> > For those not totally familiar with vi the keystrokes are
> > colon
> > percent
> > s
> > forward slash
> > control-v
> > control-m
> > forward slash
> > forward slash
> > g
> > <enter>
> > 
> > This command says to globally substitute any control-m with nothing,
> > hence removing all control-m characters with a single command.  Once
> > you are done, save the edited file (:wq!) and execute it.  You
> > should have no problems at this point.
> > 
> > 
> > Doug
> > 
> > 
> > 
> > 
> > 
> > -----Original Message-----
> > From: Tim Gardner
> > Sent: Sat 4/26/2008 12:29 AM
> > To: Rich LaReau; dl-cstech
> > Subject: RE: Help! with upgrade
> >  
> > Looks like the script got munged. Did they do something to it on
> > Windows to polute it with ^Ms?
> > Use cksum to check it against the original.
> > 
> > ________________________________
> > 
> > From: Rich LaReau
> > Sent: Fri 4/25/2008 8:43 PM
> > To: dl-cstech
> > Subject: Help! with upgrade
> > 
> > 
> > 
> > 
> > Has anybody ever had an upgrade script that just would not work?
> > I've tried to get this to run with script 3.1.0.17 and 3.1.0.14 and
> > both fail:
> > 
> > # sh EverON-3.1.0.17BC-install.sh
> > : not found0.17BC-install.sh[2]:
> > : not found0.17BC-install.sh[5]:
> > : not found0.17BC-install.sh[15]:
> > : not found0.17BC-install.sh[20]:
> > : not found0.17BC-install.sh[26]:
> > EverON-3.1.0.17BC-install.sh[104]: syntax error: `in^M' unexpected #
> > 
> > and:
> > 
> > # ./EverON-xyz.sh 
> > #  command not found 
> > 
> > Script is permissions 755, and is definitely "there"
> > 
> > This was upgrading from version 1.2.8.  I even tried to upgrade one
> > node to 2.2 as an "intermediate" version but the upgrade script will
> > not run from there either.
> > 
> > Rich
> > 
> > 
> > 
> > 
> > 
