The Linux Thread - The Autist's OS of Choice

[Betonhaus]

Drive labels are the correct way to handle this. You can easily swap out a drive by just swapping the names around, and everything is perfectly human readable.

For fucks sake I should’ve realized that labels could be used like that.

I haven't seen a distro that has had an issue like this out of the box in at least a decade, and on top of that, fstab syntax is really simple, so I don't know what's stopping you from fixing it yourself if your install is extremely old and specifies drives by how they're enumerated in /dev - or if your fstab is just missing entries altogether for some reason. Seriously, just run "sudo blkid", identify your drives, and then put the UUIDs or LABELs in your fstab.

It helps to use a gui text editor where you can copy and paste things easy enough. Nobody is typing a uuid by hand.

 

[Tom Nook's Gloryhole]

Realistically I have a vague idea of what to do; I identify the drives, I go into /etc/fstab using whatever fucking notepad equivalent I have and then when that's done I hit a command to update configs so the system is aware that fstab has changed.

But that's the thing, I DON'T WANT TO DO THIS. I know it's piss easy if you're experienced with the terminal, my issue is that almost everything major has been automated over the years APART FROM THIS. AMD drivers install automatically, sound drivers install automatically with no fucking fuss, we've got the entire fucking flatpak system that has removed the banging your head against the wall feeling with compiling software, we've got software tools for almost every issue you could possibly think of... yet something as simple as having TWO FUCKING DRIVES IN YOUR COMPUTER requires fucking with the terminal.

I just don't see how this is acceptable at all.

 

[Betonhaus]

Realistically I have a vague idea of what to do; I identify the drives, I go into /etc/fstab using whatever fucking notepad equivalent I have and then when that's done I hit a command to update configs so the system is aware that fstab has changed.

But that's the thing, I DON'T WANT TO DO THIS. I know it's piss easy if you're experienced with the terminal, my issue is that almost everything major has been automated over the years APART FROM THIS. AMD drivers install automatically, sound drivers install automatically with no fucking fuss, we've got the entire fucking flatpak system that has removed the banging your head against the wall feeling with compiling software, we've got software tools for almost every issue you could possibly think of... yet something as simple as having TWO FUCKING DRIVES IN YOUR COMPUTER requires fucking with the terminal.

I just don't see how this is acceptable at all.

Does your distro not have gnome disks? Even Linux Mint has it and setting up mounting options in it is ez

Even kde had something similar that works well. I thought you were doing a ssh into a server with how you were going on.

 

[Dante Alighieri]

While I agree with your sentiment, setting up the automounting is pretty easy and a one-and-done.

 

[acid_ra1n]

Realistically I have a vague idea of what to do; I identify the drives, I go into /etc/fstab using whatever fucking notepad equivalent I have and then when that's done I hit a command to update configs so the system is aware that fstab has changed.

But that's the thing, I DON'T WANT TO DO THIS. I know it's piss easy if you're experienced with the terminal, my issue is that almost everything major has been automated over the years APART FROM THIS. AMD drivers install automatically, sound drivers install automatically with no fucking fuss, we've got the entire fucking flatpak system that has removed the banging your head against the wall feeling with compiling software, we've got software tools for almost every issue you could possibly think of... yet something as simple as having TWO FUCKING DRIVES IN YOUR COMPUTER requires fucking with the terminal.

I just don't see how this is acceptable at all.

KDE and GNOME have GUI tools for this but learning how fstab works will be good for you in the long run
Personally I leave all of my disks off automount and get errors that soulseek can't find my drive and my dolphin pops up saying no directory and I have to enter my root password to unlock the drive every time I reboot

 

[Hakase Shinonome]

Just because I’m an annoying contrarian, fstab is the easiest shit to fix, point blank. Maybe it’s because I have certain traumatic experiences with fstab breaking five million times but I’ve done it so many times I know the syntax by hand.

/dev/nvme0n1p1 / ext4 default 0 1

If you’re not a power user, aka, a massive faggot, go use your GUI partition editor and be the faggot you were always meant to be.

Nobody is typing a uuid by hand.

When bad comes to worse…