|
|
Log in / Subscribe / Register

Introducing /run

Introducing /run

Posted Mar 31, 2011 2:42 UTC (Thu) by pyellman (guest, #4997)
In reply to: Introducing /run by cmccabe
Parent article: Introducing /run

This is the kind of crazy logic I expected, rather than something sensible. "If your looking in the root directory you're assumed to know what you're doing"? Are you serious? Same for the the "it was /var/run, so now it's just /run" argument. So what? Seems like a good time to tidy that up as well. I think the only reasonable answer I've seen yet is the "because the Unix gurus of old deemed it so". I assume at one time, it might have really mattered (in terms of limitations on path length, etc.), but those days are in the distant past.

For the record, I have introduced (or tried to introduce) Linux to a number of new users, generally from the Microsoft but some from the Apple world. Without exception, they have found the cryptic naming "conventions" for the root directory to be off-putting. Their displeasure only deepens when they are offered an explanation, and they adopt a genuine scowl when told the blunt truth: because the programmers who built the system prefer it that way.

I would venture that the cryptic root naming convention is the most immediate, visible, and universal barrier to entry for potential new Linux users. The sad part is, it doesn't have to be so.


The LWN site is currently under high scraper load, so comment display has been suppressed for anonymous users. If you are a human, you may read the comments by clicking the button below:

Note: you can avoid this step in the future by logging into your LWN account.


Copyright © 2026, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds