actkbd doesn't work under 4.0.1 anymore

[netnomad]

hi friends,

what happened with actkbd?
under microcore 3.8.4 with fluxbox it works fine.

my startup-script:

#!/bin/sh

sleep 1
if [ "`which actkbd`" ]; then
sudo killall actkbd
sudo actkbd -d /dev/input/event1 -D
sudo actkbd -d /dev/input/event3 -D
sudo actkbd -d /dev/input/event5 -D
sudo actkbd -d /dev/input/event7 -D
fi

my actkbd.conf:

113:key::ossmix vol 0
114:key::ossmix vol -- -10
115:key::ossmix vol -- +10
29+56+45:key:exec:su tc -c -l aterm &
29+125+45:key:exec:su tc -c -l lxterminal &
29+125+46:key:exec:su tc -c -l "lxterminal -e mc" &
29+56+46:key:exec:su tc -c -l ~/.wmx/Applications/mc &
29+56+48:key:exec:su tc -c -l browser &
29+56+38:rel:exec:su tc -c -l /usr/bin/exittc &
125+56+25:key:exec:su tc -c -l cpanel &
125+56+50:key:exec:su tc -c -l mnttool &
29+56+1:key:exec:su tc -c -l xkill &
56+60:key:exec:su tc -c -l ~/.wmx/SystemTools/RunProgram &

but in 4.0.1 i see no solution,
do you give me any hints or is it just a bug!?

[curaga]

Well, what are the logs/errors if any?

[netnomad]

when i start actkbd in a terminal i get no errors,
also the script mentioned above causes no errors, too.

bash-4.0$ ps waux | grep act
 5743 root     actkbd -d /dev/input/event1 -D
 5745 root     actkbd -d /dev/input/event3 -D
 5747 root     actkbd -d /dev/input/event5 -D
 6512 tc       grep act

[roberts]

Working here for me.
My particulars are:

Code: [Select]

~ $ version
microcore_4.0.1
~ $
~ $ cat actkbd.conf
125:key:noexec:
125:rep:noexec:
125:rel:exec:su tc -c aterm &
~ $
~ $ cat /opt/bootlocal.sh
#!/bin/sh
# put other system startup commands here
. /etc/init.d/tc-functions
/usr/local/sbin/actkbd -D -c /home/`cat /etc/sysconfig/tcuser`/actkbd.conf -d `getKeyEventDevice`
~ $

Where getKeyEventDevice is a little function I added to Tiny Core in v3.7

[netnomad]

hi roberts,

yeah, you gave me the right hint.
i put the slightly changed line in my .xsession and it works:

. /etc/init.d/tc-functions
sudo /usr/local/sbin/actkbd -D -c /usr/local/etc/actkbd.conf -d `getKeyEventDevice`

in /opt/bootlocal.sh no success.
in my ~./X.d/.startup i had no success, too!?
on the command line it works, but generates a loud beep.
in the .xsession it works on the first sight smoothly,
but i get in both cases an empty file called "0" in my home-dir...strange.

short question: what's the function of the dot with the space at the beginning of the command?
                         . /etc/init.d/tc-functions

and can i get rid of the "0" in my home-dir?

thank you for your kind help.

[Rich]

Hi netnomad
It's a synonym for  source  and used to execute the functions in the current shell.

[netnomad]

hi rich,

thank you for your reply.

and how can i get rid of the "0" in my home-dir?
is it o.k. to put that function into .xsession?

[maro]

It's a synonym for  source  and used to execute the functions in the current shell.

I think the second half of the sentence is a bit irritating (or almost misleading IMHO, and I know it is pretty much a direct quote from a Bash man page).

I think the important part is: When a script is run using source it runs within the existing shell, any variables created or modified by the script will remain available after the script completes

So to add (or change) environment variables (or functions) for the currently running shell one would just have to source a script that contains such export commands (or function definitions).

[netnomad]

and how can i get rid of the "0" in my home-dir?
is it o.k. to put that function into .xsession?

?

[roberts]

To get rid of 0 in home:
The function had an incorrect test for early exit,

s/b

[ $e -gt 0 ] || exit 1

Re: functions can copied directly into your script.
Your script can run at various places depending on needs and if an X environment is required.
However you may need to adjust for permissions, if run as a regular user.

[netnomad]

hi roberts,

i wasn't able to use your lines in my .xsession,
but now i got it:
probably you mean that i should change the end of your /etc/init.d/tc-functions
...

getKeyEventDevice() {
e=0
for i in /sys/class/input/input*/name; do
  if grep -q "eyboard" $i; then break; fi.
  e=`busybox expr "$e" + 1`
done
#[ $e > 0 ] || exit 1
[ $e -gt 0 ] || exit 1
echo /dev/input/event$e
}


do you want that i modify this line locally and save it over my .filetool.lst
or is it a bug that you will correct in the next release?

[roberts]

Sorry, if my prior post confused you. Yes the test line was meant for the function getKeyEventDevice and not .xsession.
I have already corrected the master and will be correct in the next release.

[netnomad]

that's fine, thank you for your reply.

[dentonlt]

It may be worth just summarizing that the event devices may have moved. Get showkey and re-test where they're going - I think I changed two in mine, as my extended/hardware keys don't go to the keyboard /dev/eventX entry.

Low stress, though. actkbd works fine.