2020-06-19
Hard-won crouton and ChromeOS directory sharing knowledgeFirst up, inside your crouton chroot, when you define mappings in /etc/crouton/shares , it's not awesomely clear from the docs, but you have to use the aliases downloads|shared|encrypted and not the literal host-side paths ~/Downloads etc.
Second, on the chronos side, hand-create ~/crouton/shared before you fire up the chroot. If it doesn't exist, it will be created in the course of opening the chroot, but it will be created under sudo and belong to root (as seen both from chronos and from the chroot), and on neither side will you be able to deal with it until you sudo chmod a bunch of voodoo. If you do create it first, then it's fine; the chronos side sees it as belonging to chronos, and the chroot sees it as belonging to your in-chroot username. Probably the same is true for the other shareable directories.
Third, if you want to share a directory that will be accessible not only to chronos command-line usage but to ChromeOS apps, you have two unappealing options. The only directory that's accessible to both is Downloads, with its threat of auto-deletion. It's already shared and you can just use it. Or you can create a directory via ChromeOS Files app, which chronos sees as falling within ~/MyFiles/ , and then go to the chronos CLI and mount your real shared directory onto that location -- so the real home of the files is ~/crouton/shared or whatever, but both the chroot and the ChromeOS GUI believe it to be at another path.
17:29
