Skip to content

Conversation

@donald
Copy link
Collaborator

@donald Donald Buczek (donald) commented Feb 4, 2023 •

Import fix from unmerged PR mariux64/mxmount#1 in mxmounts previous repository.

When booting from a usb stick, /amd/mxonastick/0 is explicitly mounted
with a label other than data0. However, if there is an existing "data0"
filesystem (e.g. on the internal hdd), this is mounted on top of it.

There is code to avoid that in mxmounts, but it doesn't work because
DEFAULT_MOUNT_PREFIX contains /amd/SHORTHOST and so the path is
compared to /amd/SHORTHOST/$hostname/0 instead of
/amd/$hostname/0.

Fixes 6c9441e ("fix data0 destination
overmount")

Copy link
Contributor

@pmenzel Paul Menzel (pmenzel) left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

… path is compared to /amd/SHORTHOST/$hostname/0 instead of /amd/SHORTHOST/$hostname/0.

The mentioned paths look identical.

When booting from a usb stick, `/amd/mxonastick/0` is explicitly mounted
with a label other than data0. However, if there is an existing "data0"
filesystem (e.g. on the internal hdd), this is mounted on top of it.

There is code to avoid that in mxmounts, but it doesn't work because
`DEFAULT_MOUNT_PREFIX` contains `/amd/SHORTHOST` and so the path is
compared to `/amd/SHORTHOST/$hostname/0` instead of `/amd/$hostname/0`.

Fixes 6c9441e ("fix data0 destination
overmount")
Sign in to join this conversation on GitHub.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants