View Single Post
Old 07-25-2013, 04:26 PM   #354
tshering
Wizard
tshering ought to be getting tired of karma fortunes by now.tshering ought to be getting tired of karma fortunes by now.tshering ought to be getting tired of karma fortunes by now.tshering ought to be getting tired of karma fortunes by now.tshering ought to be getting tired of karma fortunes by now.tshering ought to be getting tired of karma fortunes by now.tshering ought to be getting tired of karma fortunes by now.tshering ought to be getting tired of karma fortunes by now.tshering ought to be getting tired of karma fortunes by now.tshering ought to be getting tired of karma fortunes by now.tshering ought to be getting tired of karma fortunes by now.
 
Posts: 3,489
Karma: 2914715
Join Date: Jun 2012
Device: kobo touch
Quote:
Originally Posted by Markismus View Post
Yes, I can agree with that:
Line 6: mount -o remount,noatime,nodiratime /dev/mmcblk0p1 /
Line 63: mount -t vfat -o noatime,nodiratime,shortname=mixed,utf8 /dev/mmcblk0p3 /mnt/onboard

What I don't get is what would then be the cause of a completely new .kobo directory after upgrading to 2.8.1.... But if no one else experienced it, who cares.
I think, there is no "new .kobo directory". As I understand it (and I am not sure whether I understand it correctly), /mnt/onboard refers from its creation in line 26 or so up to line 62 to a directory of the system partition, and this directory gets cleared of any content in lines 45 and 46. But nothing happens at that point with reference to the user partition. Only after line 63, /mnt/onboard refers to the mounted file system. So there seems to be nothing any user could experience with regard to "her" .kobo directory.
tshering is offline   Reply With Quote