this post was submitted on 09 Jul 2024
26 points (100.0% liked)

KDE

5023 readers
105 users here now

KDE is an international technology team creating user-friendly free and open source software for desktop and portable computing. KDE’s software runs on GNU/Linux, BSD and other operating systems, including Windows.

Plasma 6 Bugs

If you encounter a bug, proceed to https://bugs.kde.org, check whether it has been reported.

If it hasn't, report it yourself.

PLEASE THINK CAREFULLY BEFORE POSTING HERE.

Developers do not look for reports on social media, so they will not see it and all it does is clutter up the feed.

founded 1 year ago
MODERATORS
carlschwan@lemmy.kde.social
Bro666@lemmy.kde.social
herzenschein@pawb.social
Aniqakhokhar@lemmy.kde.social
26
Why doesn't KDE's device auto mount just edit the /etc/fstab file? (programming.dev)
submitted 2 months ago* (last edited 2 months ago) by federino@programming.dev to c/kde@lemmy.kde.social
2 comments fedilink hide all child comments
 

Every time I tried to enable the device auto mount on my second hard drive, it never worked. I always had to manually mount it through KDE's GUI whenever I wanted to access it's content.

I later researched and found out that I could edit the /etc/fstab file with my second hard drive's UUID, which caused it to always mount on startup as I wanted.

So my question is, why doesn't KDE auto mount also replicate this process of editing the /etc/fstab?

The KDE auto mount never worked on plasma 6, I believe it's something related to wayland (even though I don't understand how they could be related).

you are viewing a single comment's thread
view the rest of the comments
[–] DarkMetatron 15 points 2 months ago

The "modern" way would use systemd to implement the mounting, either on a system or a user level. Using fstab can be problematic when the drive is missing or otherwise not available during boot.

Not sure what KDE uses exactly for auto mounting.