public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Petr Vandrovec" <VANDROVE@vc.cvut.cz>
To: wayne.brown@altec.com
Cc: linux-kernel@vger.kernel.org
Subject: [OT] ncpfs (was Re: [acme@conectiva.com.br: Re: mke2fs /dev/...)
Date: Mon, 5 Mar 2001 22:21:59 MET-1	[thread overview]
Message-ID: <138D5C448FC@vcnet.vc.cvut.cz> (raw)

On  5 Mar 01 at 15:05, Wayne.Brown@altec.com wrote:
> 
> What is the current version of ncpfs, and where can it be found?  The most
> recent I could find (at www.ibiblio.org) was ncpfs-2.2.0 which dates back to May
> 1998, and I ran into the problem with select when trying to compile it on a
> current system.  I got it to work by compiling it on an old 2.0.x box that I
> haven't upgraded in several years, then moved it to my 2.4.x system.  It's been
> working fine for several months, but I'd like to be able to compile it on a
> current system without hacking the source.

Current released version is 2.2.0.18 and is available from Debian (and
maybe RedHat and others) and from its primary site
ftp://platan.vc.cvut.cz/pub/linux/ncpfs/latest. 

Latest beta version is 2.2.0.19.pre42, and is avaialble from
ftp://platan.vc.cvut.cz/private/ncpfs (and is packaged in experimental
Debian, AFAIK).

2.2.0.19 supports TCP mode of NCP, while 2.2.0.18 supports UDP/IPX only.
2.2.0.18 compiles on libc5/glibc2.x, while 2.2.0.19 currently compiles
on glibc2.2 only.
                                                Best regards,
                                                    Petr Vandrovec
                                                    vandrove@vc.cvut.cz
                                                    

                 reply	other threads:[~2001-03-05 21:22 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=138D5C448FC@vcnet.vc.cvut.cz \
    --to=vandrove@vc.cvut.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=wayne.brown@altec.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox