I think people are confused because the difference between mount on access and mount on boot is meaningless for 98% of people. I can think of reasons to need the latter, but not many.
Comment on YouTube is taking down videos on performing nonstandard Windows 11 installs
the_riviera_kid@lemmy.world 19 hours agoarticles like this wouldn’t exist if it wasn’t true, they will appear but they wont auto mount techhut.tv/auto-mount-drives-in-linux-fstab/
BarbecueCowboy@lemmy.dbzer0.com 19 hours ago
the_riviera_kid@lemmy.world 19 hours ago
You are probably right, most folks aren’t even aware because they have no need for it. The only reason I need it is for my gaming rig that launches big picture mode on startup. I have no need for it on any of my desktop machines.
BCsven@lemmy.ca 4 hours ago
This article is more for a headless server. Any DE is going to present disks to you. And if some odd quirky drive doesn’t, you go into the disks app and click the play icon on the drive you want to mount
the_riviera_kid@lemmy.world 3 hours ago
I’ll say it again “auto mount” if you have to click on it first it’s not “auto” thats “access” mount.
BCsven@lemmy.ca 2 hours ago
Same with windows, first time you plug in it asks for drive letter, (which is mounting) if you hit ignore, that disk won’t be mounted at reboot, but if you choose a letterift will
the_riviera_kid@lemmy.world 2 hours ago
Never happens unless the drive is unformatted or a format windows can’t read. And if it is unformatted you get a pop up telling you so and an offer to format it which after that point it mounts on boot everytime without any interaction needed at all from the user. If it is already formatted it just automatically assigns the next available drive letter and mounts it. Linux just does nothing until you dig around in context menus and even after you format it it still won’t auto mount until you dig around through more menus or go through the ridiculous ftsab bullshit.