View Single Post
Old 08-06-2015, 02:38 AM   #7
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
Quote:
Originally Posted by GeoffR View Post
"reboot" is the name of a function dynamically linked from libc.so.6, so changing it in sickel should cause a relocation fault when sickel starts.
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