As I have a 1 year old rocket scientist that enjoy at pressing buttons I strongly need to disable them all, or at least to lock them (like a phone locker).
Is there anything like that I can do?
As I have a 1 year old rocket scientist that enjoy at pressing buttons I strongly need to disable them all, or at least to lock them (like a phone locker).
Is there anything like that I can do?
check keyids.py and keymap.xml
Or use an Antigrav device to levitate the box high enough so that he can't reach it.
Lol thanks.
Path to those files please?
Don't worry I know how to handle with Python files.:D
Then you should have known what find / -name filename does for you in telnet
And one of these files is an xml ...
I am not at home right now + I am a lazy guy.
OK I thought it was easier to locate the decoder hardware buttons entries, but I was wrong.
So far I haven't figured out...
edit keymap.xml will not help
http://www.dream-multimedia-tv…age=Thread&threadID=15941
create your own /etc/rc3.d/S90UserInit
(chmod 755)
with command in it
edit keymap.xml will not help
Long press power button
create your own /etc/rc3.d/S90UserInit
(chmod 755)
with command in it
I created the file like you said, rebooted completely the box and the buttons are still enabled.
However I have to say I noticed that in /etc/rc3.d/ I found only symlinks.
Did it have anyway to work?
rights(755) to execute are given?
i have file directly in folder
root@Dream8k_M3:~# ls -l /etc/rc3.d/S*
-rwxr-xr-x 1 root root 1240 Aug 12 2010 /etc/rc3.d/S00vTunerPrepare
lrwxrwxrwx 1 root root 16 Apr 27 06:34 /etc/rc3.d/S02dbus-1 -> ../init.d/dbus-1
lrwxrwxrwx 1 root root 18 Apr 27 06:34 /etc/rc3.d/S10dropbear -> ../init.d/dropbear
lrwxrwxrwx 1 root root 16 Apr 27 06:34 /etc/rc3.d/S20autofs -> ../init.d/autofs
lrwxrwxrwx 1 root root 24 Apr 27 06:34 /etc/rc3.d/S20busybox-udhcpc -> ../init.d/busybox-udhcpc
lrwxrwxrwx 1 root root 16 Apr 27 06:34 /etc/rc3.d/S20dbttcd -> ../init.d/dbttcd
lrwxrwxrwx 1 root root 17 Apr 28 16:00 /etc/rc3.d/S20hostapd -> ../init.d/hostapd
lrwxrwxrwx 1 root root 31 Apr 27 06:34 /etc/rc3.d/S20newnigma2-default-emu -> ../init.d/newnigma2-default-emu
lrwxrwxrwx 1 root root 16 Apr 27 06:34 /etc/rc3.d/S20syslog -> ../init.d/syslog
lrwxrwxrwx 1 root root 16 Apr 27 06:34 /etc/rc3.d/S20xinetd -> ../init.d/xinetd
lrwxrwxrwx 1 root root 22 Apr 27 06:34 /etc/rc3.d/S21avahi-daemon -> ../init.d/avahi-daemon
lrwxrwxrwx 1 root root 16 Apr 28 16:00 /etc/rc3.d/S65cron -> /etc/init.d/cron
-rwxr-xr-x 1 root root 1126 Jun 18 10:25 /etc/rc3.d/S90UserInit
lrwxrwxrwx 1 root root 19 Oct 17 12:03 /etc/rc3.d/S95eDaemon -> /usr/bin/eDaemon.sh
lrwxrwxrwx 1 root root 21 Apr 28 16:01 /etc/rc3.d/S95inadyn -> /etc/init.d/inadyn.sh
lrwxrwxrwx 1 root root 25 Jun 10 06:30 /etc/rc3.d/S98emustart -> /usr/script/oscam_cam.emu
lrwxrwxrwx 1 root root 22 Apr 27 06:33 /etc/rc3.d/S99rmnologin.sh -> ../init.d/rmnologin.sh
root@Dream8k_M3:~#
root@Dream8k_M3:~# cat /etc/rc3.d/S90UserInit
#!/bin/sh
[ -e /usr/bin ] || mkdir /usr/bin
[ -e /usr/keys ] || mkdir /usr/keys
[ -e /usr/script ] || mkdir /usr/script
[ -e /var/bin ] || ln -s /usr/bin /var/
[ -e /var/keys ] || ln -s /usr/keys /var/
[ -e /var/script ] || ln -s /usr/script /var/
[ -e /usr/tmp ] || ln -s /tmp /usr/
[ -e /var/tmp ] || ln -s /tmp /var/
rm /dev/input/event0 && mv `ls /dev/input/event*| tail -n1` /dev/input/event0
#[ -e /usr/script/mount_media_cf.sh ] && /usr/script/mount_media_cf.sh
[ -e /usr/script/python_patcher.sh ] && /usr/script/python_patcher.sh
[ -e /usr/script/skin_patcher.sh ] && /usr/script/skin_patcher.sh
[ -e /usr/script/AccessPoint.sh ] && /usr/script/AccessPoint.sh
route add SrvDSL gw 10.0.10.252
#route add SrvDSL gw 10.0.10.253
exit 0
root@Dream8k_M3:~#
Alles anzeigen
rights(755) to execute are given?
Yes sir.
OpenDreambox 1.6.0 dm8000
dm8000 login:
Password:
root@dm8000:~# ls -l /etc/rc3.d/S*
lrwxrwxrwx 1 root root 16 Jan 1 2000 /etc/rc3.d/S02dbus-1 ->
../init.d/dbus-1
lrwxrwxrwx 1 root root 14 Jan 1 2000 /etc/rc3.d/S09sshd -> ..
/init.d/sshd
lrwxrwxrwx 1 root root 15 Jan 1 1970 /etc/rc3.d/S20inetd -> .
./init.d/inetd
lrwxrwxrwx 1 root root 16 Jan 1 1970 /etc/rc3.d/S20syslog ->
../init.d/syslog
lrwxrwxrwx 1 root root 16 Jan 1 1970 /etc/rc3.d/S20vsftpd ->
../init.d/vsftpd
lrwxrwxrwx 1 root root 16 Jan 1 1970 /etc/rc3.d/S21autofs ->
../init.d/autofs
lrwxrwxrwx 1 root root 22 Jan 1 2000 /etc/rc3.d/S21avahi-daem
on -> ../init.d/avahi-daemon
lrwxrwxrwx 1 root root 24 Dec 11 2012 /etc/rc3.d/S21cron -> /e
tc/init.d/busybox-cron
-rwxr-xr-x 1 root root 88 Oct 25 16:26 /etc/rc3.d/S90UserInit
lrwxrwxrwx 1 root root 24 Jul 3 09:50 /etc/rc3.d/S99cron -> /e
tc/init.d/busybox-cron
lrwxrwxrwx 1 root root 17 Sep 13 2012 /etc/rc3.d/S99nemesis ->
../init.d/nemesis
lrwxrwxrwx 1 root root 19 Sep 13 2012 /etc/rc3.d/S99rmnologin
-> ../init.d/rmnologin
root@dm8000:~# cat /etc/rc3.d/S90UserInit
#!/bin/sh
rm /dev/input/event0 && mv `ls /dev/input/event*| tail -n1` /dev/input/event0roo
t@dm8000:~#
Alles anzeigen
your image is two years outdated, but at this problem it doesn't have to make sense
maybe on your image `input` devices are loaded in different order, try remove other numbers, one on each attempt
#!/bin/sh
#rm /dev/input/event0 && mv `ls /dev/input/event*| tail -n1` /dev/input/event0
rm /dev/input/event1 && mv `ls /dev/input/event*| tail -n1` /dev/input/event1
#rm /dev/input/event2 && mv `ls /dev/input/event*| tail -n1` /dev/input/event2
#rm /dev/input/event3 && mv `ls /dev/input/event*| tail -n1` /dev/input/event3
#rm /dev/input/event4
OK I found the entry in keymap.xml and deleted it.
Now my son cannot completely shutdown the decoder anymore, but I still would like to disable all the buttons.
show please what changes you have made
also long(2 sec) + short + short doesn't send box to deep standby?
show please what changes you have made
also long(2 sec) + short + short doesn't send box to deep standby?
The answer to the second question is no.
What I did was completely removing the following entry and doing a full decoder restart:
If you cange the keyid in keyids.py to a dummy (like 999) then the key(s) would not be recognized anymore by enigma2.
And be aware that an enigma2 update will revert the changes you made, so be prepared to re-do them.
If you cange the keyid in keyids.py to a dummy (like 999) then the key(s) would not be recognized anymore by enigma2.
And be aware that an enigma2 update will revert the changes you made, so be prepared to re-do them.
Great I am gonna try it right now.
Thanks!