From owner-freebsd-current Mon Feb 24 22:20:30 2003 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 941) id 7D8E537B401; Mon, 24 Feb 2003 22:20:28 -0800 (PST) Date: Mon, 24 Feb 2003 22:20:28 -0800 From: "Tim J. Robbins" To: freebsd-current@freebsd.org Subject: netncp/nwfs is rotting... Message-ID: <20030224222028.A93044@hub.freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG A few months ago there was a thread on this list discussing the state of NWFS/netncp/libncp/etc. on 5.0. Terry Lambert produced a patch [1] that made netncp compile. The patch still applies cleanly to -current and almost compiles; I broke it with ncp_ncp.c rev 1.13, adding #includes of sys/lock.h and sys/mutex.h fixes it. However, even with this patch, ncp.ko still does not load because the aout_sysvec symbol is not available. After patching ncp_load() to use SYS_MAXSYSCALL instead of elf_sysvec.sv_size, the module loads but crashes in ncp_timer(): ncp_load: [210-213] Fatal trap 12: page fault while in kernel mode fault virtual address = 0x10 fault code = supervisor read, page not present instruction pointer = 0x8:0xc1027d39 stack pointer = 0x10:0xc5b9cc8c frame pointer = 0x10:0xc5b9cc9c code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, IOPL = 0 current process = 12 (swi6: clock) Even after that has been fixed, there are plenty of other bug fixes that need to be backported from smbfs. Is anyone still working on updating netncp/nwfs for 5.0? I think that it should be retired to the Attic if nobody has any plans to fix it before we create the RELENG_5 branch. Tim [1] http://marc.theaimsgroup.com/?l=freebsd-current&m=103835435100398&w=2 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message