Kindle & RAR

[silver18]

Originally Posted by eureka

Use the absolute path:

/mnt/us/unrar e /mnt/us/example.rar

I get a Permission Denied error...

Originally Posted by knc1

But unzip'ing the file takes time and file space.
If your Kindle supports FUSE ( and I think it does), then you just have to mount the *.zip file like any other filesystem device:
http://code.google.com/p/fuse-zip/
Once you have that installed on your Kindle.
Your application program will never know the difference between a *.zip file and the for-real filesystem on /mnt/us.

Nice!!!
I need to study it....so many thing to know...

[knc1]

Originally Posted by silver18

I get a Permission Denied error...

Use the "ls -l" (-ell) command to list the permissions of both unrar and the archive.

The manual extraction from the *.deb probably didn't set the execute bit on unrar:

chmod +x unrar

[silver18]

Unrar has 0755...
And I can't change it to 0777...

[knc1]

Originally Posted by silver18

Unrar has 0755...
And I can't change it to 0777...

755 is good enough, execute permission for anyone.

Now check example.rar permissions, looking for read permissions (digits will contain '4' in them).

Cheatsheet:
4 - read
2 - write
1 - execute
for a total of 7 in each digit postition (plus other stuff, ot here).
I.E: 5 == read, execute

[silver18]

Also rar file is 755....
Unzip, in /usr/bin is 777

[knc1]

Originally Posted by silver18

Also rar file is 755....
Unzip, in /usr/bin is 777

Which is either an error or just the permissions of a symbolic link to Busybox.


Do you have write permission on the destination the extracted files will be written to?

Hint: if you can create a new, empty file with 'touch filename.txt' then you do have write permission there. (and 'rm filename.txt' when done with it).

[silver18]

Originally Posted by knc1

Which is either an error or just the permissions of a symbolic link to Busybox.


Do you have write permission on the destination the extracted files will be written to?

Hint: if you can create a new, empty file with 'touch filename.txt' then you do have write permission there. (and 'rm filename.txt' when done with it).

Everything is ok. I can read/write in /mnt/us....
Anyway, I tried to get rw permission on root (mntroot rw), nothing changed!
I downloaded this package

[eureka]

Originally Posted by silver18

Everything is ok. I can read/write in /mnt/us....
Anyway, I tried to get rw permission on root (mntroot rw), nothing changed!
I downloaded this package

I've downloaded the same package, took unrar-nonfree binary, copied it to /mnt/us on KT, then tried to execute /mnt/us/unrar-nonfree e /mnt/us/example.rar (while being in temporary, manually created /mnt/us/t directory). Archive was unpacked without problems.

example.rar had been taken from first Google result for example rar query.

I think, I can't help you any further.

[silver18]

Finally I got it working....
I had to unpack it again using another online unpacker service...

Now it works really fine!

Thanks to everyone!

Last question:
if I run unrar from /mnt/us, everything works, but if I run it from /mnt/base-us, I get again the permission error...Why?

[knc1]

Originally Posted by silver18

Finally I got it working....
I had to unpack it again using another online unpacker service...

Now it works really fine!

Thanks to everyone!

Last question:
if I run unrar from /mnt/us, everything works, but if I run it from /mnt/base-us, I get again the permission error...Why?

different filesystem, different permissions.

Do the "touch & rm (remove)" check to see if you can write in that part of the tree.

Note: You can rename that binary from unrar-nonfree to something else (unrar maybe?) That is just a bit of en_Debian style naming.

[eureka]

/mnt/base-us is mounted with noexec option.

[geekmaster]

/mnt/base-* mounts are always READ-ONLY. The mount points without "base-" are the writable mount points.

It is a bad idea to mount a partition writeable twice with different mount points.

[knc1]

Originally Posted by eureka

/mnt/base-us is mounted with noexec option.

Good point, I forgot to mention checking for that permission.
Hmm... But the message should have been different. Could Silver be editing these error messages before posting? Naw, he wouldn't do that to us, would he?

[silver18]

I always worked in base-us folder....create and delete files wasn't ever a problem!!
I get the permission denied error only if working in base-us, but not in us.
I can't understand why, as I can do whatever I want in base-us!

[knc1]

Originally Posted by silver18

I always worked in base-us folder....create and delete files wasn't ever a problem!!
I get the permission denied error only if working in base-us, but not in us.
I can't understand why, as I can do whatever I want in base-us!

As posted above, file system is mounted with noexec option (forbids execution of your unrar binary).
Both individual files and entire filesystems have permission controls.
(if confused at this point, just be glad Kindles don't run selinux or use acl lists.)

Just put the unrar binary someplace without that restriction (/mnt/us/bin?) and refer to it by its full pathname on the command line.
(or change your PATH env. variable to include /mnt/us/bin in the search list)