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’re the only one rambling about coding right now, Apocalypteroid just used the word once; given he’s a self-described novice it’s safe to assume the word was used in a generalizing manner to describe any kind of bash, command line magic or config file syntax (as little as there is, there still is more or less basic syntax you have to adhere to. Enthusiasts might not even realize this anymore).
Your comments do make a good example of the communication problem between novices and Linux/IT enthusiasts though. Your expectation towards people who aren’t into a topic to use perfect terminology in their questions is both naive and inconsiderate. It’s no wonder people got angry with you.
To answer your last question regarding “understand filesystem (paradigms)”: Coming from Windows people rarely, if ever, had to learn about any kind of filesystem; if they had to most people just right-clicked and formatted a disk. While saying that “ext4 is standard” would be rather straight-forward, more and more distros come with btrfs. Additionally it’s important to know about exfat to not let them run into awful situations with incompatible USB sticks and such. Of course this can and should be shown using their distro’s native Disk Utility, i.e. Gnome Disks, KDE Partition Manager or whatever comes with or at a minimum a common tool like GParted so they can safely interact with their own devices.
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.
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’re the only one rambling about coding right now, Apocalypteroid just used the word once; given he’s a self-described novice it’s safe to assume the word was used in a generalizing manner to describe any kind of bash, command line magic or config file syntax (as little as there is, there still is more or less basic syntax you have to adhere to. Enthusiasts might not even realize this anymore). Your comments do make a good example of the communication problem between novices and Linux/IT enthusiasts though. Your expectation towards people who aren’t into a topic to use perfect terminology in their questions is both naive and inconsiderate. It’s no wonder people got angry with you.
To answer your last question regarding “understand filesystem (paradigms)”: Coming from Windows people rarely, if ever, had to learn about any kind of filesystem; if they had to most people just right-clicked and formatted a disk. While saying that “ext4 is standard” would be rather straight-forward, more and more distros come with btrfs. Additionally it’s important to know about exfat to not let them run into awful situations with incompatible USB sticks and such. Of course this can and should be shown using their distro’s native Disk Utility, i.e. Gnome Disks, KDE Partition Manager or whatever comes with or at a minimum a common tool like GParted so they can safely interact with their own devices.
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.