Description

Follow on from #11777 (comment).

To the naive user of a system with multiple mounted filesystems the behaviour of

$ mpremote cp foo.py :  

seems nondeterministic, because the destination of the copy can only be established with knowledge of the state of the target (its current directory). The same applies to

$ mpremote ls : 

The following change would provide a deterministic and more discoverable interface.

1. Where there is only one mounted filesystem, behaviour remains exactly as currently.
2. Where there are multiple filesystems behaviour is as follows:

mpremote ls : produces a list of mountpoints (as per ls : /).
mpremote cp foo.py : throws an exception because you cannot write to '/'.
mpremote cp foo.py :/sd/ works as at present.

While this is a breaking change, an inability to write to '/' will not surprise anyone familiar with the MP directory structure.

Code Size

No response

Implementation

I hope the MicroPython maintainers or community will implement this feature

Code of Conduct

Yes, I agree