yeah well I think you did got ahead of me with scripts but well done.

BTW I like to keep it simple....when you boot and find no event 5 or 6.....I could have said run that command back in rc.local but name the event something you never had...like event7.....would that save you work?

I have tryed to do so, but the remote will be assigned at one of those inputX by the module ir-kdb-i2c (needed by the remote itself) without the "link" to lircd. If I start lircd with another inputX not assigned to the remote by the kernel (I think) it doesn't work as if I don't set the inputX argument when I lunch the command.
I booted several times both the kernels, and each time the mouse and the remote work. A very dirty but very reliable solution. ;)