HP3000-L Archives

May 1999, Week 2

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Chris Bartram <[log in to unmask]>
Reply To:
Date:
Wed, 12 May 1999 13:48:11 -0400
Content-Type:
Text/Plain
Parts/Attachments:
Text/Plain (42 lines)
 In <[log in to unmask]> [log in to unmask] writes:

> Jeff Kell wrote:
>
> > [log in to unmask] wrote:
> >
> > > Re: Thoughts on FTP/iX enhancements
> >
> > Overall, love it!
> >
> > > 4. POSIX PUT
> > > 5. POSIX GET
> > > ____________
> > >
> > > There is no need to have a "./" prefix to put/get POSIX files
> > > However, to get a file from the non-default account, you
> > > need to specify the file in HFS, i.e. /ACCOUNT/GROUP/file;
> > > file.GROUP.ACCOUNT WILL NOT work.
> >
> > Fine, provided this works around the "filename.ext" ambiguity with
> > filename.groupname we have now.
> >
> > > 6.  ASCII get of bytestream files
> > > _________________________________
> > >
> > > Currently, if you specify ASCII option and do a "get" of bytestream
> > > file, you get a "CR-LF" after each character.  The ASCII get of a
> > > bytestream file should effectively result in a "binary" get.
> >
> > Not sure I follow here, at least the binary get part; that's the
> > problem (binary transfer) isn't it, getting the newline terminator
> > in a supposedly flat text file?  I'd like posix mode ASCII gets/puts to
> > create a bytestream file.
>
> yeah -- what jeff said! :-)             - d

Me3.

I'll even beta test!

   -Chris Bartram

ATOM RSS1 RSS2