inputtrap ??

bridged with qdn.public.qnxrtp.os
Post Reply
Alain Bonnefoy

inputtrap ??

Post by Alain Bonnefoy » Tue Jan 06, 2004 3:02 pm

Hi,
According to the doc, it seems that the command 'inputtrap' probes the
hardware and displays the necessary relevant command line to start
devi-hirun.

If I start 'inputtrap', I get nothing!!!!

'inputtrap -v' says:
Probing : keyboard
/dev/kbd exists, using....
Probing: ps2
Found ps2 mouse. Assuming interrrupt 12.
Probing: ....
.....

it seems that inputtrap found something but why does it display nothing
without '-v' option?

Alain.

James MacMillan

Re: inputtrap ??

Post by James MacMillan » Tue Jan 06, 2004 3:02 pm

You are not, by any chance, running this command from within a pterm in
Photon, are you?

Alain Bonnefoy wrote:
Hi,
According to the doc, it seems that the command 'inputtrap' probes the
hardware and displays the necessary relevant command line to start
devi-hirun.

If I start 'inputtrap', I get nothing!!!!

'inputtrap -v' says:
Probing : keyboard
/dev/kbd exists, using....
Probing: ps2
Found ps2 mouse. Assuming interrrupt 12.
Probing: ....
....

it seems that inputtrap found something but why does it display nothing
without '-v' option?

Alain.

James MacMillan

Re: inputtrap ??

Post by James MacMillan » Tue Jan 06, 2004 3:02 pm

Please disregard my last post. I was mis-remembering. I thought this
sounded familiar. It has already been fixed but was not critical enough
to be put out as a patch. It will definitely be in the next release.

A little history:
It used to be that inputtrap would print out its commandline by default.
The only problem with this is that it cluttered up the console with info
that people rarely cared about. It was reported as a problem and the
printout was removed. Unfortunately, it was completely removed and no
alternative was put in place before release. The new inputtrap scheduled
for the next release adds a "query" option which specifies that you wish
to see the commandline printed out.

James MacMillan wrote:
You are not, by any chance, running this command from within a pterm in
Photon, are you?

Alain Bonnefoy wrote:

Hi,
According to the doc, it seems that the command 'inputtrap' probes the
hardware and displays the necessary relevant command line to start
devi-hirun.

If I start 'inputtrap', I get nothing!!!!

'inputtrap -v' says:
Probing : keyboard
/dev/kbd exists, using....
Probing: ps2
Found ps2 mouse. Assuming interrrupt 12.
Probing: ....
....

it seems that inputtrap found something but why does it display
nothing without '-v' option?

Alain.

Alain Bonnefoy

Re: inputtrap ??

Post by Alain Bonnefoy » Wed Jan 07, 2004 8:04 am

ok thanks!


James MacMillan a écrit:
Please disregard my last post. I was mis-remembering. I thought this
sounded familiar. It has already been fixed but was not critical enough
to be put out as a patch. It will definitely be in the next release.

A little history:
It used to be that inputtrap would print out its commandline by default.
The only problem with this is that it cluttered up the console with info
that people rarely cared about. It was reported as a problem and the
printout was removed. Unfortunately, it was completely removed and no
alternative was put in place before release. The new inputtrap scheduled
for the next release adds a "query" option which specifies that you wish
to see the commandline printed out.

James MacMillan wrote:

You are not, by any chance, running this command from within a pterm in
Photon, are you?

Alain Bonnefoy wrote:

Hi,
According to the doc, it seems that the command 'inputtrap' probes
the hardware and displays the necessary relevant command line to
start devi-hirun.

If I start 'inputtrap', I get nothing!!!!

'inputtrap -v' says:
Probing : keyboard
/dev/kbd exists, using....
Probing: ps2
Found ps2 mouse. Assuming interrrupt 12.
Probing: ....
....

it seems that inputtrap found something but why does it display
nothing without '-v' option?

Alain.


Post Reply

Return to “qdn.public.qnxrtp.os”