4 ms·

I use Arch Linux and I haven't faced any of the problems you mention. I don't game so this might be slightly skewed, but there's not a single thing on Windows t

I use Arch Linux and I haven't faced any of the problems you mention. I don't game so this might be slightly skewed, but there's not a single thing on Windows that would tempt me into using it. Also the sudo point I completely disagree with. It comes down to security or convenience, and it's a damned shame that people pick convenience.

Skunkleton 10y ago
Further, if you are doing a bunch of administrative tasks from the CLI, sudo will keep you authenticated. If you really want, you could even open up a root shell. I think the real problem is that the Right Way(tm) to do things is completely non obvious to a linux novice. Looking back on my times starting out with linux (ubuntu 6.06), I remember a lot of similar frustrations. Really, there is no middle ground, you are either a novice or an expert, and bridging that gap is super challenging. The only real useful advice I ever received was to 1) learn the CLI, and don't assume that it is antiquated, 2) use linux for real tasks, don't just follow tutorials, and 3) If something isn't working the way you want it to, there is probably a way to change it. Hopefully the author will use his frustrations as a learning experience, rather than a reason to leave the platform. The linux community could use more people like him.
- eitland 10y ago
  > If you really want, you could even open up a root shell. For those new to Linux: this can be done as simple as "sudo su -". More details here: http://askubuntu.com/questions/376199/sudo-su-vs-sudo-i-vs-sudo-bin-bash-when-does-it-matter-which-is-used http://askubuntu.com/questions/376199/sudo-su-vs-sudo-i-vs-s... That said, -in my book using root except for updates is often a sign that someone misunderstood or that something is misconfigured or something.
  - gdamjan1 10y ago
    > sudo su - sudo -i
- gdamjan1 10y ago
  > Really, there is no middle ground, you are either a novice or an expert, and bridging that gap is super challenging. I think it's easier now. Also, the "expert" level on windows… it's mindbogling complex.
  - libeclipse 10y ago
    Windows has an intermediate level though. The average consumer never gets past novice.
- jodrellblank 10y ago
  I think the real problem is that the Right Way(tm) to do things is completely non obvious to a linux novice. I can't see Unicode characters properly over SSH, because it claims my locale is "POSIX". I'd like to fix it the right way, is it: http://askubuntu.com/questions/162391/how-do-i-fix-my-locale-issue http://askubuntu.com/questions/162391/how-do-i-fix-my-locale... - locale-gen; dpkg-reconfigure locales, with 293 upvotes and 96 "didn't work for me" - setting the environment variables in /etc/environment, with 225 upvotes - setting them in /etc/default/locale, with 70 upvotes - exporting them from .bashrc on a per-user basis, with 70 upvotes - editing ssh_config and removing the option to SendEnv, with 53 upvotes - Install the language-pack-en-base, 23 upvotes - exporting environment variables from /etc/bash.bashrc, on a system-wide basis, 9 upvotes - exporting them from /etc/profile or .bash_profile, for 6 upvotes OR http://askubuntu.com/questions/770309/cannot-permanently-change-locale-on-16-04-server http://askubuntu.com/questions/770309/cannot-permanently-cha... - localectl set-locale, from systemd OR http://serverfault.com/questions/626346/ssh-locale-wrong http://serverfault.com/questions/626346/ssh-locale-wrong - UsePAM directive in sshd_config, which turns on Pluggable Authentication Modules and in a sneaky and ridiculous rider, also turns on 'session module processing for all authentication types', and disable locale setting if you disable PAM OR https://serverfault.com/questions/475925/how-to-fix-putty-showing-garbled-characters/475930 https://serverfault.com/questions/475925/how-to-fix-putty-sh... - change /etc/pam.d to make the pam_lsass.so 'optional' instead of 'sufficient' How many of those are 'obvious' to an expert?

Skunkleton 10y ago

Further, if you are doing a bunch of administrative tasks from the CLI, sudo will keep you authenticated. If you really want, you could even open up a root shell. I think the real problem is that the Right Way(tm) to do things is completely non obvious to a linux novice. Looking back on my times starting out with linux (ubuntu 6.06), I remember a lot of similar frustrations. Really, there is no middle ground, you are either a novice or an expert, and bridging that gap is super challenging. The only real useful advice I ever received was to 1) learn the CLI, and don't assume that it is antiquated, 2) use linux for real tasks, don't just follow tutorials, and 3) If something isn't working the way you want it to, there is probably a way to change it. Hopefully the author will use his frustrations as a learning experience, rather than a reason to leave the platform. The linux community could use more people like him.

eitland 10y ago
> If you really want, you could even open up a root shell. For those new to Linux: this can be done as simple as "sudo su -". More details here: http://askubuntu.com/questions/376199/sudo-su-vs-sudo-i-vs-sudo-bin-bash-when-does-it-matter-which-is-used http://askubuntu.com/questions/376199/sudo-su-vs-sudo-i-vs-s... That said, -in my book using root except for updates is often a sign that someone misunderstood or that something is misconfigured or something.
- gdamjan1 10y ago
  > sudo su - sudo -i
gdamjan1 10y ago
> Really, there is no middle ground, you are either a novice or an expert, and bridging that gap is super challenging. I think it's easier now. Also, the "expert" level on windows… it's mindbogling complex.
- libeclipse 10y ago
  Windows has an intermediate level though. The average consumer never gets past novice.
jodrellblank 10y ago
I think the real problem is that the Right Way(tm) to do things is completely non obvious to a linux novice. I can't see Unicode characters properly over SSH, because it claims my locale is "POSIX". I'd like to fix it the right way, is it: http://askubuntu.com/questions/162391/how-do-i-fix-my-locale-issue http://askubuntu.com/questions/162391/how-do-i-fix-my-locale... - locale-gen; dpkg-reconfigure locales, with 293 upvotes and 96 "didn't work for me" - setting the environment variables in /etc/environment, with 225 upvotes - setting them in /etc/default/locale, with 70 upvotes - exporting them from .bashrc on a per-user basis, with 70 upvotes - editing ssh_config and removing the option to SendEnv, with 53 upvotes - Install the language-pack-en-base, 23 upvotes - exporting environment variables from /etc/bash.bashrc, on a system-wide basis, 9 upvotes - exporting them from /etc/profile or .bash_profile, for 6 upvotes OR http://askubuntu.com/questions/770309/cannot-permanently-change-locale-on-16-04-server http://askubuntu.com/questions/770309/cannot-permanently-cha... - localectl set-locale, from systemd OR http://serverfault.com/questions/626346/ssh-locale-wrong http://serverfault.com/questions/626346/ssh-locale-wrong - UsePAM directive in sshd_config, which turns on Pluggable Authentication Modules and in a sneaky and ridiculous rider, also turns on 'session module processing for all authentication types', and disable locale setting if you disable PAM OR https://serverfault.com/questions/475925/how-to-fix-putty-showing-garbled-characters/475930 https://serverfault.com/questions/475925/how-to-fix-putty-sh... - change /etc/pam.d to make the pam_lsass.so 'optional' instead of 'sufficient' How many of those are 'obvious' to an expert?