2006-12-06: Bob Copeland dixit: > I've personally not had that happen and did riocp -b a bunch of > times, but I guess I wasn't "lucky."
I used -b many times long time ago, when debuging the smaldb code. Once it was considered free of bugs, I also run riocp -b many times, without troubles. One should take into account, however, that I do keep my *1 files in "good condition". I mean, you can write whatever you like in these files; both legal and ilegal properties and/or property values. Thanks to the USB interface, you may even edit these files manually at will! RK Rescan Music seems to do a very good job in parsing the *1 files and getting rid or ignoring all the strange staff found in these files. But I think the corresponding code in libkarma is not as robust and mostly assumes that *1 files contents is "correct". So it may happens that it is not a matter of luck: "riocp -b" might very well produce a corrupted smalldb from corrupted *1 files! My 2 cents (of Euro ;) Best, EV. ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ linux-karma-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/linux-karma-devel
