Re: Lynx and binary files

1996-09-14 Thread Brian C. White
  (a)   Content-type: application/GNU Compr. Tar
 
  (b)   Content-type: text/plain
 
  The question now is, who tells lynx to identify these files?
 
 It's normal - look at lynx.cfg file and modify it - it should contain lot
 of lines with first word SUFFIX (it tels how to transfer different filetypes)
 an add lines like:
 
 SUFFIX:.deb:application/octet-stream
 SUFFIX:.tgz:application/octet-stream
 
 I think that in Debian version of Lynx file lynx.cfg should at least contain
 first line!!!

If Lynx reads /etc/mime.types, then both of these are already defined.

application/x-debian-packagedeb
application/x-gtar  gtar tgz
 
  Brian
 ( [EMAIL PROTECTED] )
 
---
 measure with micrometer, mark with chalk, cut with axe, hope like hell



Lynx and binary files

1996-09-13 Thread Martin Schulze
Good day folks,

I've been runnning into a problem with lynx and download of files.

In an ftp-listing I try to download two files

(a) x.tar.gz
and
(b) x.deb

Case (a) works without any problem, but the downloaded file (b) isn't
usable.  I then took look at the ftpserver and found out that (a) was
fetched in binary mode, but for (b) an ascii connection was used.

Before downloading lynx shows the following (not exactly)

(a) Content-type: application/GNU Compr. Tar

(b) Content-type: text/plain

The question now is, who tells lynx to identify these files?



Re: Lynx and binary files

1996-09-13 Thread Martin Schulze
Hiho,

Seems that I have found what I was looking for. Lynx reads
/etc/mime.types and the file from 1.1 didn't contain an entry for
*.deb files. The mime-support package from the unstable tree does.

Sorry for disturbing,

Joey

-- 
Individual Network e.V._/  OrgaTech KG
[EMAIL PROTECTED]_/  [EMAIL PROTECTED]
Geschaeftszeit: Di+Fr, 15-18 Uhr _/Tel: (0441) 9808556



Re: Lynx and binary files

1996-09-13 Thread bigl
On Fri, 13 Sep 1996, Martin Schulze wrote:

 Good day folks,

Ex Equo :-)

 Before downloading lynx shows the following (not exactly)
 
 (a)   Content-type: application/GNU Compr. Tar
 
 (b)   Content-type: text/plain
 
 The question now is, who tells lynx to identify these files?
 

It's normal - look at lynx.cfg file and modify it - it should contain lot 
of lines with first word SUFFIX (it tels how to transfer different filetypes)
an add lines like:

SUFFIX:.deb:application/octet-stream
SUFFIX:.tgz:application/octet-stream

I think that in Debian version of Lynx file lynx.cfg should at least contain 
first line!!! 


Leszek Gerwatowski
[EMAIL PROTECTED]



Re: Lynx and binary files

1996-09-13 Thread Christopher R. Hertel
This is being handled by the 'mime.types' file.  I don't really know
enough about it, but I'll take a shot in hopes that it will help.

The remote server has a mime.types file that tells it what
Content-type: line to write out.  You should be able to fix the problem
by getting the site maintainer to add the 'deb' extension to the
'application/octet-stream' line.

It might also work to add 'deb' to the 'application/octet-stream' of
the mime.types file that Lynx is using at your end.  I'm not sure if
this will work, but it's worth a try.

Good luck!

Chris -)-

On Sep 13,  1:26pm, Martin Schulze wrote:
 Subject: Lynx and binary files
: Good day folks,
:
: I've been runnning into a problem with lynx and download of files.
:
: In an ftp-listing I try to download two files
:
: (a)   x.tar.gz
: and
: (b)   x.deb
:
: Case (a) works without any problem, but the downloaded file (b) isn't
: usable.  I then took look at the ftpserver and found out that (a) was
: fetched in binary mode, but for (b) an ascii connection was used.
:
: Before downloading lynx shows the following (not exactly)
:
: (a)   Content-type: application/GNU Compr. Tar
:
: (b)   Content-type: text/plain
:
: The question now is, who tells lynx to identify these files?
-- End of excerpt from Martin Schulze



-- 
Christopher R. Hertel -)-   University of Minnesota
[EMAIL PROTECTED]  Networking and Telecommunications Services