Well, that's umm, special.

I wonder if powering off the printer isn't causing the sysctl to be removed,

causing the next power-on to look like a new device ?

Eric, you poked around the sysctl paths in parport last year, any ideas?
	Dave
--

http://www.codemonkey.org.uk

Yes.  The short answer is that this is a real bug in the parport code

that has existed forever.  We just now complain.
http://bugzilla.kernel.org/show_bug.cgi?id=9749
It takes something like two accessors of the parallel port to trigger

this.  Though not in a bad way.
In particular each open creates the sysctl for the duration of the

open (or something like that) and so if you open (I think it is

/dev/parport0) twice you try and create the sysctls twice.
I got as far as basic confirmation of this bug, and a rough cause of

it.  Unfortunately I have not had the time to unscramble it, and neither

it seems has anyone else.
Eric

--