Glad I could help.
I have no idea what this mean is even trying to say, but as someone who is trying to make the switch to Linux, it is a steep learning curve, even for the most “user-friendly” distros.
A lot of the information in forums assumes some sort of basic knowledge of code and processes which aren’t readily available. I’ve asked a few noob questions and while there are some helpful people out there, there are also a fuck load of assholes who seem to think they walked out the womb speaking Ubuntu.
So my message to those people is, if you’re not gonna be helpful, kindly keep your snide comments to yourself.
If gou have an issue shoot me a message, I can’t guarantee anything but i’ll try to help
Shoot me a message too. I don’t know anything about Linux but I’m lonely.
If you’re getting coding advice, you might be on the wrong forums, which can explain the snark.
You don’t need to do code to use Linux. You can use Bash if you want, but it’s not a necessity
Too many people expect you to know and understand gnu-utils and all the common config file, filesystem and folder structure paradigms though. Which is the problem.
The problem is that Linux nerds, myself included, are too deep in the knowledge to even think of sth. You might not know. And my way to learn the basics of Linux was breaking 3 installations and running random scripts from stack overflow without really knowing what they do.
I don’t want this the way for new people to learn Linux. There must be a better way. But I don’t know which one. People who think you can’t ask questions because your basics are missing should shut the fuck up and go to 4chan or so.
None of that is code.
It’s possible that when you ask for help you don’t even use the words correctly, like you demonstrated here, so you expect people to help you without doing a bare minimum of even understanding the terms. If this is true, it’s on you.
So many times I saw people comming hot, asking for help, and when given a command to run, getting angry that it’s some words they don’t understand, and asking for a different solution, one that doesn’t require commands.
I don’t know, for example, what problem you had that required you to “understand filesystem” whatever you mean by that, and if so, what solution to it you expected.
You can use Bash if you want, but it’s not a necessity
I would argue and say at minimum you should be comfortable with Bash and the file system , otherwise if you spend a year running Linux and encounter some obscure error you’ll be totally clueless troubleshooting wise and might end up breaking something else.
