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.
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.
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
[–]BCsven@lemmy.ca0 points1 day ago* (last edited 1 day ago)
(1 children)
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 letter it will
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.
Not true, if you format a NTFS or fat in windows, then remove drive letter, it won't auto Mount, same I'd you format it in Linux to a windows format and add to your PC, it prompts for a drive letter.
As for Linux, your user session defaults determine if it automounts or not.
Mine USD set to automount, so you can see in this screen the 80gig drive was auto mounted, but you can turn off USD and use specific mount options.
Running Tubleweed with Gnome, and the App is Disks. The user session defaults are accessed via dconf editor and you can set your system wide default for auto mounting, or manually tweak each drive via disks.I
Yast Partitioner was other screenshots, also has options to do the same if you run KDE tumbledweed, or you could install Disks.
I have tried both over the years. KDE rally has some great customization, but I come back to GNOME because it feels like the while DE is purposefully designed. GNOME Disks has built in backup and restore ISO files also, which I have found helpful for SDcards duplication. And there is an option to attach Isos or image files so you can mount them as loop devices and see the contents inside.
Say what? That's not true in the slightest, if the drive is mountable it will show up in your file manager.
articles like this wouldn't exist if it wasn't true, they will appear but they wont auto mount https://techhut.tv/auto-mount-drives-in-linux-fstab/
*some distros may auto mount but I never used one that did
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.
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.
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
I'll say it again "auto mount" if you have to click on it first it's not "auto" thats "access" mount.
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 letter it will
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.
Not true, if you format a NTFS or fat in windows, then remove drive letter, it won't auto Mount, same I'd you format it in Linux to a windows format and add to your PC, it prompts for a drive letter.
As for Linux, your user session defaults determine if it automounts or not. Mine USD set to automount, so you can see in this screen the 80gig drive was auto mounted, but you can turn off USD and use specific mount options.
collapsed inline media
What desktop environment/distro are you using? It would be nice to be able to skip the fstab run around and just click a button.
Running Tubleweed with Gnome, and the App is Disks. The user session defaults are accessed via dconf editor and you can set your system wide default for auto mounting, or manually tweak each drive via disks.I
Yast Partitioner was other screenshots, also has options to do the same if you run KDE tumbledweed, or you could install Disks.
collapsed inline media
Hey thanks! this is actually helpful. Why KDE can't just have this as well is a mystery but oh well I'll try Gnome.
I have tried both over the years. KDE rally has some great customization, but I come back to GNOME because it feels like the while DE is purposefully designed. GNOME Disks has built in backup and restore ISO files also, which I have found helpful for SDcards duplication. And there is an option to attach Isos or image files so you can mount them as loop devices and see the contents inside.