- Feature Articles
- CodeSOD
- Error'd
-
Forums
-
Other Articles
- Random Article
- Other Series
- Alex's Soapbox
- Announcements
- Best of…
- Best of Email
- Best of the Sidebar
- Bring Your Own Code
- Coded Smorgasbord
- Mandatory Fun Day
- Off Topic
- Representative Line
- News Roundup
- Editor's Soapbox
- Software on the Rocks
- Souvenir Potpourri
- Sponsor Post
- Tales from the Interview
- The Daily WTF: Live
- Virtudyne
Edit Admin
I was so ready for the non-ascii 4th character of "Janči" to be the problem.
Admin
I did have to fix a Windows + non-ASCII char + ssh key problem once. It wasn't pleasant. It involved three icacls $path commands whenever the key was changed.
Admin
Those "Linux users", always troublemakers, something always doesn't work for them. Why cannot they just be normal?
Admin
Frankly if you ask me all operating systems were just a bad idea. The moment you start adding layers between your code and the bare metal is the moment you give up on quality and performance both.
Sure, they look great on the brochure. Run any program on any machine. Newer have to worry about hardware specs. Etc. Etc. What they don't tell you is that this comes at the cost of introducing dependencies on the work of people you can't trust with all the bugs that come with it. And you can forget about optimization too since you can't optimize for unknown hardware.
Yuck to it all I say. :)
Edit Admin
Some Unix tools (e.g.
chown) allow you to specify users and groups either by name or uid. Having an all-numeric username will confuse them, so it's a Bad Idea even if the system technically allows it. For this reason, account management tools likeuseraddusually prohibit them (and for simplicity they just check that the first character is not a digit).The WTF should be that he wasn't informed of this when he first created the account. And if this guy is a "veteran", he should have known about this.