this post was submitted on 06 Feb 2024
620 points (98.9% liked)
Technology
59979 readers
2312 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related content.
- Be excellent to each another!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, to ask if your bot can be added please contact us.
- Check for duplicates before posting, duplicates may be removed
Approved Bots
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
lsblk outputs that my NVMe0n1p1 is mounted at /var/snap/Firefox/common/host-hunspell.
This drive and partition is where my root is.
lsblk
is just lacking a lot of information and creating a false impression of what is happening. I did a bind mount to try it out.This mounts
/var/log
to/mnt
without making any other changes. My root partition is still mounted at/
and fully functional. However, all thatlsblk
shows under MOUNTPOINTS is/mnt
. There is no indication that it's just/var/log
that is mounted and not the entire root partition. There is also no mention at all of/
.findmnt
shows this correctly. Omitting all irrelevant info, I get:Here you can see that the same device is used for both mountpoints and that it's just
/var/log
that is mounted at/mnt
.Snap is probably doing something similar. It is mounting a specific directory into the directory of the firefox snap. It is not using your entire root partition and it's not doing something that would break the
/
mountpoint. This by itself should cause no issues at all. You can see in the issue you linked as well that the fix to their boot issue was something completely irrelevant.