I'm pretty sure I'm going to have to do something at the NetBSD
	end to handle MacOS X's bizarre behaviour here, but I'd though I'd
	check on this list to see if anyone had any thoughts.

	When trying to print from a MacOS X box to a NetBSD server via
	lpd the MacOS box sends everything with a job number of 1. This
	interacts badly if the first job is still in the queue when the
	second one arrives (such as printing from freehand). The server
	tries to rename the cf file over the previous one and rejects the
	job.

	Has anyone seen this or similar? Should NetBSD's lpd be handling
	this case and just assigning a new print job ID?

-- 
		David/absolute		abs@formula1.com