Edit - Unix & Linux Stack Exchange

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

My goodness, very helpful. I think that gets me going in the right direction. It also clarifies what are system vs operator files. Misconceptions muddy the water and I think you've demuddied the waters quite a bit for me. Even though I kind of braindumped up there I feel I now have a great starting place. If I have any real issues that cannot be answered by referring to your response I will continue the conversation, but it looks like I'll be able to get my head around this now. Very well articulated answer, sir. Thank you!

thursDave
– thursDave

2018-04-11 15:57:32 +00:00
Commented Apr 11, 2018 at 15:57

Add a comment |

Correct minor typos or mistakes
Clarify meaning without changing it
Add related resources or links
Always respect the author’s intent
Don’t use edits to reply to the author

create code fences with backticks ` or tildes ~
```
like so
```
add language identifier to highlight code
```python
def function(foo):
print(foo)
```
put returns between paragraphs
for linebreak add 2 spaces at end
_italic_ or **bold**
indent code by 4 spaces
backtick escapes `like _so_`
quote by placing > at start of line
to make links (use https whenever possible)

<https://example.com>

[example](https://example.com)

<a href="https://example.com">example</a>

formatting help »
answering help »