No, you are correct and I am correct. It understands links that are between items in the source tree. That is if you have a tree of music and you have created some links that point _within that tree_, then his program will detect that, maintain structure and only upload the file once.

However, if you have a master tree, and create a source tree using symlinks to the master tree, his program will not work. At least I couldn't make it. I even checked into looking to add that functionality. But all the code for the inter-tree link detection was in the way, so it wasn't easy to find where to add.

Oh, I see. I hadn't looked that hard. You could conceivably make one hard link with the rest soft links to it, but that'd be a pain to administer.

But even using hard links, soft links etc, and then automating all that, it's still not very good compared to:

Rsync (from the player to the pc) the symlink farm, which includes the database files.
Remove symlinks from the current symlink farm.
Run a selection routine, this generates a filelist.
Create new symlinks based on filelist.
Rsync (from the pc to the player) the symlink farm.

One thing that is nice, is that it's about as few steps as possible. And the only "cludgy" thing is that rsync doesn't take a filelist, that would be ideal.

The main thing is that I can transfer database changes back from the player to the pc, and then use information gathered there to pick the songs that are next.

Correct me if I'm wrong, but the writeable parts of the database are, to my knowledge, a big binary blob on that extra partition right? That's not as fun to play with as a simple text based one. Granted my current implementation isn't so fast, but it's fast enough (start up tiime -- defined as starting of music playing -- is a hair faster than the default player. But it does take about 30 seconds to finish reading the rest of the database).

Anyway, an easy to work with database is one of the reasons I wrote Squash. The second was to improve the shuffle mode (which is 95% of the time what I used). And the third was to support OGG's since that meant I could have more music on the player (I went from 3200 MP3's to 4000 OGG's). The last reason was so I would have a player at home on my pc (Squash runs on the PC (using console/ncurses), not just the empeg).

There was a brown paper bag null derefernce in the 1.0 release. Please use the 1.0.1 release if it affected you.

I put the files on savannah.gnu.org, but they don't seem to be showing up. So just use the CVS until I decide where else to host this project because savannah is reallllllllly making me upset.

Thought I would bring this thread back from the dead to see if anybody knew what happened to gryng? Schofield's post got me thinking about replacement player software and it seems like squash was the closest thing we ever had to a viable alternative, but Adam disappeared just about the time it started working

-Mike

Do you still have his email address? The atmosphere is a lot different now, so people might be more open to trying this out. Even if he doens't have fime to develope it, I'm sure he might have some advice on what he was doing. It seems like most BBS members now have 2 or more players, so we'd be willing to try this out on a second player.

[email protected] according to freshmeat.

I would like to put my teeth in Squash when I soon get my second and third player. We really need an open-source player for our beloved Empeg

Audun