From: Petr Vandrovec <vandrove@vc.cvut.cz>
To: Alexandre Hautequest <hquest@fesppr.br>
Cc: linux-kernel@vger.kernel.org
Subject: Re: IPX in 2.4.[5-9]
Date: Tue, 21 Aug 2001 01:45:17 +0200 [thread overview]
Message-ID: <20010821014517.G1394@ppc.vc.cvut.cz> (raw)
In-Reply-To: <998343425.3b818301718cd@webmail.fesppr.br>
In-Reply-To: <998343425.3b818301718cd@webmail.fesppr.br>
On Mon, Aug 20, 2001 at 06:37:05PM -0300, Alexandre Hautequest wrote:
> Hello all.
>
> What's the actual IPX support in linux? Is it broken since 2.4.7? Or i just need
> to recompile my tools against a new kernel version -- the old ones was compiled
> in a 2.4.5 -- with any patch, option, whatever?
>
> hquest@condor:~$ dmesg
> (snip)
> IPX Portions Copyright (c) 1995 Caldera, Inc.
> IPX Portions Copyright (c) 2000, 2001 Conectiva, Inc.
> hquest@condor:~$ /sbin/ifconfig -v eth0
> eth0 Link encap:Ethernet HWaddr 00:00:F8:08:BD:A1
> inet addr:172.16.40.2 Bcast:172.16.255.255 Mask:255.255.0.0
> IPX/Ethernet 802.2 addr:AC100000:0000F808BDA1
> (snip)
> hquest@condor:~$ slist
> slist: Server not found (0x8847) in ncp_open
> hquest@condor:~$ _
>
> Not flaming anyone, just questioning.
If you do not have ncpfs-2.2.0.16, but anything newer, or older than 2.2.0.12,
then it should work. If it reports 8847, it means that you have misconfigured
network (search for 8847 on support.novell.com). You have either no server
on 802.2, or you (or admin) disabled Reply To Get Nearest Server on all
servers connected to your wire. You must enable it at least on one of them.
Best regards,
Petr Vandrovec
vandrove@vc.cvut.cz
next prev parent reply other threads:[~2001-08-21 0:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-20 21:37 Alexandre Hautequest
2001-08-20 23:45 ` Petr Vandrovec [this message]
2001-08-21 12:01 ` Alexandre Hautequest
2001-08-21 12:38 ` kees
2001-08-21 23:06 ` Petr Vandrovec
2001-08-21 0:47 ` Arnaldo Carvalho de Melo
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=20010821014517.G1394@ppc.vc.cvut.cz \
--to=vandrove@vc.cvut.cz \
--cc=hquest@fesppr.br \
--cc=linux-kernel@vger.kernel.org \
/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
all inboxes | Powered by JetHome®