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

[email protected]

620

Mozilla’s new service tries to wipe your data off the web (www.theverge.com)

submitted 10 months ago by [email protected] to c/[email protected]

72 comments fedilink hide all child comments

Mozilla has launched a paid subscription service called Mozilla Monitor Plus, which monitors and removes personal information from over 190 sites where brokers sell data.
The service is priced at $8.99 per month and is an extension of the free dark web monitoring service Mozilla Monitor (previously Firefox Monitor).
Basic Monitor members receive a free scan and one-time removal sweep, while Plus members get continual monthly data broker scans and removal attempts.

Archive link: https://archive.ph/YdY3R

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 4 points 10 months ago

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.

sudo mount -o ro --bind /var/log /mnt

This mounts /var/log to /mnt without making any other changes. My root partition is still mounted at / and fully functional. However, all that lsblk 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:

TARGET                                                SOURCE                 [...]
/                                                     /dev/dm-0              [...]
[...]
└─/mnt                                                /dev/dm-0[/var/log]    [...]

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.