Re: automount doesn't work without GPT table

[Alexander Shiyan <eagle.alexander923@gmail.com>]

Hello.

> > The error occurs in the cdev_mount_default() function.
> > cdev_get_mount_path() returns "/boot".
> > And indeed, the partition is mounted here for some reason...
> > I don't understand yet why this happens.
> >
> > barebox@Mega-Milas Informer SAMA5D2:/ mount
> > none on / type ramfs
> > none on /dev type devfs
> > /dev/mmc1.0 on /boot type fat
> >
> > Update:
> > I found that this happens if the CONFIG_OF_BAREBOX_ENV_IN_FS option is used.
> > When disabled, mounting occurs as expected, but in this case I cannot
> > use environments from a file from a partition on the SD card.
> > It is not yet clear how to get out of this situation...
>
> Ok, so the partition is already mounted for the environment to /boot, so
> you get -EBUSY when trying to automount it somewhere else.
>
> The question arises why you want to access it via automount when you
> already mounted it for your environment.

Mounting the FULL partition with the environment file to /boot was a
surprise to me :)
I just expected the usual behavior of the automount command.

Thanks!