View Single Post
Old 08-06-2015, 02:42 AM   #33
frostschutz
Linux User
frostschutz ought to be getting tired of karma fortunes by now.frostschutz ought to be getting tired of karma fortunes by now.frostschutz ought to be getting tired of karma fortunes by now.frostschutz ought to be getting tired of karma fortunes by now.frostschutz ought to be getting tired of karma fortunes by now.frostschutz ought to be getting tired of karma fortunes by now.frostschutz ought to be getting tired of karma fortunes by now.frostschutz ought to be getting tired of karma fortunes by now.frostschutz ought to be getting tired of karma fortunes by now.frostschutz ought to be getting tired of karma fortunes by now.frostschutz ought to be getting tired of karma fortunes by now.
 
frostschutz's Avatar
 
Posts: 2,282
Karma: 6123806
Join Date: Sep 2010
Location: Heidelberg, Germany
Device: none
With a pre-3.16.10 firmware (a firmware without sickel) the hack will be there but ignored. With a post-3.16.10 firmware (a firmware with sickel) the hack will be gone and you have to re-apply.

As GeoffR pointed out in the other thread there is a potential this might break the binary; it does not for 3.16.10 but it's hard to make guarantees for future versions.

Quote:
Originally Posted by frostschutz View Post
Yes, that's what I assumed but - it actually runs, it runs, it pings, it works in every aspect, but when it actually triggers the reboot - it dies, with relocation fault, and nickel (if still alive) subsequently starts a new instance which is back in ping-mode.
frostschutz is offline   Reply With Quote