Hi, This may be a bit outdated, but I am now reviewing old messages of the list which I could not reply in due time...
2006-12-08: Bob Copeland dixit: > > [...] I had what I assumed to be corrupt mp3 files on my > > Karma (or a potentially bad hard drive). So I deleted all > > playlists and files off of my Karma through it's user > > interface. Now, when I mount my Karma's partitions, the fids0 > > directory appears completely empty, and I am unable to use > > riocp or lkarmafs. > > There was a bug at one time (maybe it never got fixed), that an > empty database caused everything to break. [...] Well, it is not really a bug. If an empty (0 bytes) file exists as .../var/smalldb, then everything seems to work as expected. Of course, you get some warnings/errors, but that's O.K. If you upload a file (using e.g., riocp, then smalldb gets populated and, from this point on, everythink works as usual. The problem comes if no .../var/smalld exists, because its existance is checked as the ultimate guarantee that the given or discovered mount point is really a RK disk. If it is not found, the "connection" is refused and everything else is aborted. So, all you need is to just mount the RK at some RK-MOUNT-POINT and then "touch $RK-MOUNT-POINT/var/smalldb". May be an option could be added to riocp to make this empty smalldb upon demand. 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
