KUAL: Kindle Unified Application Launcher (v2.7)

[NiLuJe]

@kmcbest: not stuck? Then what's the problem?

Regardless, check the first post again, what you need is probably MKK.

[kmcbest]

@NiLuJe: thanks but I've followed along the steps, I've installed MKK (Update_mkk-20140214-k4-ALL_install.bin) and update my Kindle. It is the kindlet step which runs in problem.

[NiLuJe]

@kmcbest: Then we're gonna need more details.

[abrunho]

I've just upgraded from v2.2 (build 20130816) on my Kindle PW (firmware 5.3.4) and the "Replace Store button / Restore Store button" option on the KUAL+ submenu doesn't work anymore... Everything's OK when I revert back to v2.2.

[NiLuJe]

@abrunho: Yup, update the KUAL add-ons extension. I should have fixed it to work w/ the new version (untested, though).

[abrunho]

Originally Posted by NiLuJe

@abrunho: Yup, update the KUAL add-ons extension. I should have fixed it to work w/ the new version (untested, though).

Thank you NiLuJe!

Everything works fine now, after updating the add-ons/helper extensions.
I didn't notice any improvements by installing the GNU Awk, though.

[NiLuJe]

@abrunho: Great, thanks for confirming that it works .

As for GNU Awk, provided you ran the install from the KUAL menu, it's mostly noticeable if you have a lot of extensions installed (or a few complex ones), on the first startup & on menu refreshes .

[richy1989]

My Kpw1 had updated from 5.3.9 to 5.4.4 this morning.
But the KUAL didn't work.

[dsmid]

@richy1989: Install MKK.

[richy1989]

@dsmid
I had installed MKK
But it doesn't work too.

Do you have a try?

[NiLuJe]

@richy1989: Define "doesn't work". We're gonna need way more details than that.

[chrox]

Originally Posted by NiLuJe

@richy1989: Define "doesn't work". We're gonna need way more details than that.

Yes. Almost all hacks are dead since the new firmware mounts `/mnt/us` in `noexec` option.

The `fstab` in firmware 5.4.4 reads:

# /etc/fstab: static file system information.
#
# <file system>   <mount pt>    <type> <options>                                         <dump>  <pass>
/dev/mmcblk0p1    /             ext3   suid,exec,auto,nouser,async,rw,noatime,nodiratime 0      1
proc              /proc         proc   defaults                                          0      0
sysfs             /sys          sysfs  defaults                                          0      0
devpts            /dev/pts      devpts defaults,gid=5,mode=620                           0      0
usbfs             /proc/bus/usb usbfs  defaults                                          0      0
/dev/loop/0       /mnt/base-us  vfat   defaults,noatime,nodiratime,utf8,noexec,uid=0,gid=0,umask=0,shortname=mixed              0      0
/dev/mmcblk1p1    /mnt/base-mmc vfat   defaults,noatime,nodiratime,utf8,noexec,shortname=mixed              0      0
fsp#/mnt/base-us  /mnt/us       fuse   allow_other,umask=0,uid=0,gid=0,rw,max_write=65536,max_readahead=65536,noatime,noexec,nosuid,nodev,nonempty     0      0
fsp#/mnt/base-mmc /mnt/mmc      fuse   rw,max_write=65536,max_readahead=65536,noatime,exec,nosuid,nodev,nonempty     0      0

[dsmid]

@chrox: You're wrong, 5.4.2.1 fstab is the same and executing from /mnt/us/ works.

EDIT:
Anyway, /mnt/us/ being executable before can be due to a bug (upstart scripts? fuse?) and this bug has been maybe addressed in the new firmwares.
Creating file /MNTUS_EXEC should make /mnt/us executable again.
I believe it should be added to jailbreak or MKK.

[chrox]

Originally Posted by dsmid

@chrox: You're wrong, 5.4.2.1 fstab is the same and executing from /mnt/us/ works.

EDIT:
Anyway, /mnt/us/ being executable before can be due to a bug (upstart scripts? fuse?) and this bug has been maybe addressed in the new firmwares.
Creating file /MNTUS_EXEC should make /mnt/us executable again.
I believe it should be added to jailbreak or MKK.

Anyway if I unmount /mnt/us and remount /mnt/us in exec mode, I bring back koreader in firmware 5.4.4. I think there is something wrong with the mounting options.

umount /mnt/us
mount -t fuse -o rw,max_write=65536,max_readahead=65536,noatime,exec,nosuid,nodev,nonempty fsp#/mnt/base-us /mnt/us

Is there anything more elegant to remount a fuse filesystem in exec mode? Probably we need to add this snippet in the launching script in koreader.

[dsmid]

@chrot: Take a look at /etc/upstart/userstore, fstab is pretty much ignored when mounting the userstore, it all depends on options passed to script /usr/sbin/mntus .
As I wrote, create file /MNTUS_EXEC and reboot. Userstore should be mounted in exec mode.