CLICK HERE ===> https://tinurll.com/2sMJQk
hmm, there are three different builds of mplayer. the three different architectures (ppc, x86, arm), with binary files of three different sizes (386, 440, 486). i guess i'll have to set up the ppc build by hand, as i don't have an arm machine available. and it's not as if i've much experience with building large, complex packages for ppc, in particular. got to a ppc build of mplayer today, but the arm version was somewhat more popular. i now have a large pile of.dmg files. the ppc ones are the ones that were the most recent. there's a file release/readme.mpc, but no release/readme.dmg, which was the ppc version. after some more work, i found the problem was not quite where i thought. it is not the rsync, which should be the synchronisation of the local file system with the server one. in fact, the rsync is the very last thing that happens. there's a difference between a transfer and a sync: a transfer merely updates the local file system with the contents of the server's. it's still possible to have partial files, in case the client is interrupted. a sync, on the other hand, is a more cooperative protocol, which ensures the correct order of the files. at least the first one (the one i just started, and it was running a while) was taking too long to start. so the problem is not the rsync, but something else, which is probably related to not having any local file system. i tried updating the file system, which brings my file system up-to-date with itself: 01100000-01180000 rw-p 00000000 00:00 0 01200004-01250000 rw-p 00000000 00:00 0
98329e995e
https://open.firstory.me/story/cldnygqat0dnq01t43qrlddwo https://open.firstory.me/story/cldmc4wiy0bu301t48sxc7b8b https://open.firstory.me/story/cldnydam60qhn01tjag7heecn https://open.firstory.me/story/cldnygqat0dnq01t43qrlddwo https://open.firstory.me/story/cldnydam60qhn01tjag7heecn