

Pretty much. As a windows user it’s like conversing in another language (literally) so I was saying 'do not try to learn to speak the native language, just use a translator"


Pretty much. As a windows user it’s like conversing in another language (literally) so I was saying 'do not try to learn to speak the native language, just use a translator"


I’ll probably put that image on my desktop for permanent reference just in case because it is good to understand how engines work even if you never plan on even changing the oil yourself.


I didn’t say they did. In fact, I say not to.


I set up my mom’s laptop with clamtk (set to auto update definitions), auto backup, and auto update
OOC (I have no idea what that is) how long did it take you to first learn how to do that, and more importantly, how long would it have taken your mother to learn it had you not?


This is a better summary than many that are out there even still…
Is that file a bin or opt? oh, it’s an opt linked in bin. No no, it’s a usr/bin my bad.
Like I understand that people smarter than I felt this is the way, but you have to admit this is a lot if a newbie needs to know this for some reason. Thankfully, I don’t need to.


The oldest drivers I could find in the repository are 4.2 something I think and their installation crashed. All the other versions don’t enable 1080i (it looks like a stripped blurry mess) including the Nouveau. F’ing with XrandR didn’t help, and the Xorg.conf file ended up crashing my boot to CLI login and at that point I gave up. I’ve seen others have the exact same issue and nobody had relevant advice that worked based on what I could see. I now just set the resolution to the highest one that uses progressive scan and live with that. It’s my own fault for saving $500 like 20 years ago. :P


Yeah, people seem to be thinking I’m criticizing needing to use the CLI but I’m glad I learned it too. It’s empowering to the point it’s cliche. I just feel it isn’t communicated well that ‘user CLI awareness’ needs to be emphasized more. Otherwise, the existential dread of booting to the CLI login prompt with no GUI in sight would destroy newbies.


Ironically, I set it up using virtualbox instead of any CLI BS and the only aggravation is UEFI changing the boot order anytime anything gets changed on the stick but I get it so np.


Based on the data that even Mint, the overwhelming consensus being it is the most user friendly distro available, deemed it necessary to put the terminal on the taskbar. That, and if anything goes wrong and the bootup fails, it defaults to the command line interface.
I had horrible experience with Bazzite. Installer somehow corrupted a separate win10 installation on another drive, I couldn’t get Samba 1 to connect to a network share, ‘ujust updating’ caused boot to black screen, and in general the online support is abysmal compared to older more established distros like Ubuntu.
Wiped and installed (win10 again, and) Mint fixed all the issues. Samba 1 unlocking works so the network drive is accessible, updated everything with one click and it didn’t crash on reboot, both OS’s appear in the boot list, and it being much older the support is far easier to obtain as a newbie.
Literally just installed Mint (and reinstalled), a couple days ago so I’m as wet behind the ears as they come. IMO the people recommending Bazzite don’t care of their system breaks and it takes 2 hours to fix every 2nd week (I assume this will improve as you gain xp with the BS/Bazzite Software).