PRS-500 Mountable Sony Reader Filesystem

[scotty1024]

Originally Posted by VladSukhoy

couple more reports:
* cannot create directories (at least in /media/books)
* does not like concurrent access with two programs (at least with two Finders, I've never seen "ghost files" in finder before... ).

Add the directory issue to the firmware update list.

scotty$ mkdir sony/Reader/tmp/test
mkdir: test: Operation not permitted
scotty$ mkdir sony/Card/test
scotty$ ls -dl sony/Card/test
drwxrwxrwx   2 root  wheel  0 Feb 13 05:43 sony/Card/test
scotty$ rmdir sony/Card/test

I've tried all the directories on the reader with my debug goodies turned on and the Sony refuses to create directories in any of them. But I can create all the directories I want on the memory card.

[VladSukhoy]

I have the old firmware.. Don't want to upgrade unless there really is a reason to.
libprs500 can do it, readerfs cannot (but still can make 'em on SD).

[scotty1024]

Found it. The internal filesystem requires a trailing / on directories. The SD filesystem doesn't.

[Xenophon]

Originally Posted by scotty1024

OK, here it is, version 0.2 of the mountable Sony Reader Filesystem for Mac OS X 10.4.8.

This is a Universal Binary with support for Intel and Power PC.

...SNIP...

Scotty --

It doesn't appear to be a universal binary! At least, when I try to run it, I get

[Scipio:~/Documents/Downloads] dfsuther% ./readerfs
tcsh: ./readerfs: Bad CPU type in executable.
[Scipio:~/Documents/Downloads] dfsuther%

Of course, I could be misunderstanding the intended usage of the executable. After all, I haven't found any docs on how one is expected to install or use a MacFUSE filesystem... MacFUSE says that's "up to the filesystem program" (whatever that means).

After poking around a bunch, I guessed that perhaps I should try connecting my reader and firing up the downloaded executable, thus getting the message above.

?help?

Xenophon

[adinb]

I was able to get it to mount on my ICBM; gave it a mountpoint and it worked like a charm.

I had my PRS-500 plugged in on a "good" port already (because I was playing around with biblioskop), so I'm not sure if that had anything to do with my own good luck. I'm also running .2.1 of the core, so that might help.

I'm getting a lot of stalls when I try to navigate too far into the directory structure, hopefully scotty'll be able to iron those out in future releases. He's doing an incredible job with the fuse plugin tho!

-a

[scotty1024]

Originally Posted by Xenophon

...SNIP...

Scotty --

It doesn't appear to be a universal binary!

There are two versions of the code posted here, one is not a Universal Binary and the other one is. I'll give you one guess as to which one I think you are using.

You want the 0.2 version.

To date all FUSE filesystem plug-ins follow this basic usage pattern.

Device or service to be mounted needed to inserted or available prior to running the plug in.

You need a folder pre-created to mount them on to.

In Terminal:

mkdir MySonyReader <--- but can be anything you want: Dog, Cat, favorite Rugby Team etc...

Then you run the FUSE plugin naming that folder as the mount point.

In Terminal:

readerfs MySonyReader

Depending on how your path is setup in Terminal you may need to use:

/FolderReaderfsWasUnZippedInto/readerfs MySonyReader

To turn off the plug.

In Terminal:

umount MySonyReader

[scotty1024]

I've tested the mountable filesystem on Fedora Core 6 and it is working great.

What version of Linux is anyone using here that would want this filesystem? Please let me know so I can package it for you.

[Xenophon]

Originally Posted by scotty1024

There are two versions of the code posted here, one is not a Universal Binary and the other one is. I'll give you one guess as to which one I think you are using.

You want the 0.2 version.

To date all FUSE filesystem plug-ins follow this basic usage pattern.
...snip good info on using the plug-in...

Scotty --
I am using the 0.2 version. The problem is that you compiled for the "ppc970" (which is to say the G5). My machine is a G4 (MDD FireWire800, to be precise). So, I get the following:

[Scipio:~/Documents/Downloads] dfsuther% ls -lt ./readerfs
-rwxr-xr-x   1 dfsuther  staff  59444 Feb 12 15:24 ./readerfs
[Scipio:~/Documents/Downloads] dfsuther% mkdir readertest
[Scipio:~/Documents/Downloads] dfsuther% ./readerfs readertest
tcsh: ./readerfs: Bad CPU type in executable.
[Scipio:~/Documents/Downloads] dfsuther% file ./readerfs
./readerfs: Mach-O fat file with 2 architectures
./readerfs (for architecture i386):     Mach-O executable i386
./readerfs (for architecture ppc970):   Mach-O executable ppc
[Scipio:~/Documents/Downloads] dfsuther%

Perhaps you might build with the -mcpu=powerpc instead of -mcpu=970 flag? Or maybe something else rather odd is happening...

Xenophon

[ghostwheel]

I am using kubuntu, so for me a debian package would be great!

Thanks!

[scotty1024]

Originally Posted by Xenophon

Scotty --
I am using the 0.2 version. The problem is that you compiled for the "ppc970" (which is to say the G5). My machine is a G4 (MDD FireWire800, to be precise). So, I get the following:

[Scipio:~/Documents/Downloads] dfsuther% ls -lt ./readerfs
-rwxr-xr-x   1 dfsuther  staff  59444 Feb 12 15:24 ./readerfs
[Scipio:~/Documents/Downloads] dfsuther% mkdir readertest
[Scipio:~/Documents/Downloads] dfsuther% ./readerfs readertest
tcsh: ./readerfs: Bad CPU type in executable.
[Scipio:~/Documents/Downloads] dfsuther% file ./readerfs
./readerfs: Mach-O fat file with 2 architectures
./readerfs (for architecture i386):     Mach-O executable i386
./readerfs (for architecture ppc970):   Mach-O executable ppc
[Scipio:~/Documents/Downloads] dfsuther%

Perhaps you might build with the -mcpu=powerpc instead of -mcpu=970 flag? Or maybe something else rather odd is happening...

Xenophon

Now it makes sense. I compiled for the Power PC but accidentally optimized for the G5.

Sorry about that.

[scotty1024]

OK, this version is not over optimized on the Power PC, it will work on G4's.

It also implements over writing existing files and has the fix for deleting directories.

[scotty1024]

I've got the automatic card detection working.

The code sorts out how to access MS or SD cards, and if you have no card, doesn't provide the Card folder.

[Xenophon]

Originally Posted by scotty1024

I've got the automatic card detection working.

The code sorts out how to access MS or SD cards, and if you have no card, doesn't provide the Card folder.

Version 0.4 now runs fine on my G4 PowerMac. I have a few questions:

• Should I expect to see more than 0K available on either the card or the reader's main memory? (Note that there is actually space available on both.)
• Deleting a book from the main memory works fine. Should I expect to be able to copy that book back into main memory? I currently get a "no space available" message when I try. (Likely related to my first question.)
• Should I expect a File->GetInfo command to work on any folder on the reader? Current behavior was a very long SPoD, followed by no result.

I'm really psyched by the progress you folks are making hacking stuff for the reader. I eagerly look forward to having multiple non-Sony utilities to choose among for Sony Reader goodness...

Xenophon

[brett.brennan]

Originally Posted by scotty1024

I've tested the mountable filesystem on Fedora Core 6 and it is working great.

What version of Linux is anyone using here that would want this filesystem? Please let me know so I can package it for you.

My wife and I have a bunch of SuSE 10.x machines (laptops & servers) so anything that provides 2.6 kernel compatibility should be OK. RPM or source.

[J.D. Northrup]

Strangely enough, I've found that some files get corrupted while they're being transferred to the reader. I'm attaching a zip file with a document before and after it gets copied using the readerfs.

Any ideas anyone?

These are created using the flatLrf library with some modifications, but they appear kosher to the Sony Connect program on the PC.

-jd