[HEADSUP] IPX and NWFS to be killed in -current.

Poul-Henning Kamp phk at phk.freebsd.dk
Mon Dec 6 02:24:27 PST 2004


In message <41B43140.802 at freebsd.org>, Scott Long writes:
>Poul-Henning Kamp wrote:
>> We are aiming 6.X at production readiness around start of 2006.
>> 
>> By that time IPX and NWFS are not really interesting and nobody
>> seems to be interested in doing the SMPng work on them.
>> 
>> I propose we remove them from -current before the 6.x freeze starts
>> next spring.
>> 
>
>Are these getting in the way of current work? 

That's not really the most relevant question is it ?

I would think that the question is

   "Will we be comfortable with listing them in our feature list for 6.x ?"

This could also be phrased as:

   "Do we actually have somebody who will make sure it works ?"

or even:

   "Does anybody care about PR's against the code and does it even work ?"

This last one I think we can answer:

Hint:

S	Submitted	Tracker	Resp.	Description	
f	2001/12/13	kern/32797 	glebius	[netgraph] Problem with IPX and netgraph(4)	
o	2003/03/06	kern/48976 		nwfs.ko oddity	
a	2003/11/12	kern/59211 		[nwfs] System crashes when moving files from NWFS mounted system	
p	2004/04/05	kern/65217 	bms	PATCH: Improve Linux IPX application compatibility	
o	2004/04/23	kern/65920 		[nwfs] Mounted Netware filesystem behaves strange	
o	2004/07/15	kern/69100 		[nwfs] panic: 5.2.1p9 kernel panics when mounting nwfs filesystem	
o	2004/08/10	kern/70236 		[patch] uninitialised parameters passed to kernel_sysctl [nwfs_vfsops.c smb_subr.c]	
o	2004/11/19	kern/74105 	rwatson	IPX protocol support doesn't work	

-- 
Poul-Henning Kamp       | UNIX since Zilog Zeus 3.20
phk at FreeBSD.ORG         | TCP/IP since RFC 956
FreeBSD committer       | BSD since 4.3-tahoe    
Never attribute to malice what can adequately be explained by incompetence.


More information about the freebsd-arch mailing list