The Linux Thread - The Autist's OS of Choice

  • 📧 If you are an employee of a T1 ISP, US datacenter, or related company please get in touch at josh@kiwifarms.net. I have some questions.
  • Want to keep track of this thread?
    Accounts can bookmark posts, watch threads for updates, and jump back to where you stopped reading.
    Create account
Susanna said:
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.
Click to expand...
For fucks sake I should’ve realized that labels could be used like that.
Eternal Gopnik said:
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.
Click to expand...
It helps to use a gui text editor where you can copy and paste things easy enough. Nobody is typing a uuid by hand.
 
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.
 
Tom Nook's Gloryhole said:
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.
Click to expand...
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.
 
Tom Nook's Gloryhole said:
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.
Click to expand...
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
 
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.

Betonhaus said:
Nobody is typing a uuid by hand.
Click to expand...
When bad comes to worse…
 
SchizoDaemon said:
You can copy and paste things in the terminal and copy things to the terminal.

There are quite a number of cheatsheets online that are well worth learning.

e.g.

Click to expand...
I’m never going to remember the magical commands to select text from the output of thr command to get uuid, much easier to use the mouse to highlight the text and copy and use a notepad to move text around. I know it’s doable but for the amount of times I need to do it I’m not going to remember
 
You are just pretending it is more difficult than it is. Keyboard shortcuts are in almost every GUI program, and people manage to use them fine, but if you suggest people look up a cheatsheet for a terminal, for whatever reason that is too much of an ask. I find it tiresome.

I have to deal with these two mongoloids at work; if I ask them to do something they can Google, they want me to show them. At first I was nice to them and did so. Now I just tell them to fucking google it or read the fucking README that I wrote for them.

Part of the whole philosophy of using Linux and open source in general is that you are in control and you take responsibility, not hand it off to a third party to do it for you.
 
Betonhaus said:
select text from the output of thr command to get uuid,
Click to expand...
This is where text editor skill comes in handy because :r! blkid in vim just shits the entirety of blkid into wherever your cursor is.
 
You must log in or register to reply here.
Back
Top Bottom