View Single Post
Posts: 18 | Thanked: 72 times | Joined on Sep 2008
#17
Originally Posted by ThePooBurner View Post
Does mlocker.so need to be chmod'ed in anyway before one does this?
It shouldn't need to be, it's in the archive with the right permissions. But, if you extract it to a VFAT partition (like in MyDocs), it might get messed up. If you want to be on the safe side, go ahead and chmod 755 the library once it's in place. It doesn't need to be SUID, though, if that's what you mean.

In other news I got started with mlock'ing those other binaries and promptly reboot-looped my N900. It took me the better part of five hours to get it running again because EARLY_SSH in kernel-power didn't work as advertised (see my post on the k-power thread for the solution). So I had to try and fix things in the rootfs filesystem using the meego rescue initrd, which was complicated because I didn't understand ubifs at all.

For anyone else that falls into that trap (assuming you're using the meego rescue initrd, or any other initrd that gives you a standard shell):

1. Append ubi.mtd=rootfs to the kernel command line.
2. Type at the shell prompt: mount -t ubifs ubi0:rootfs /mnt