I do not wish to sound ungrateful as I am aware that without this AU I would be pretty much lost. However, sometimes the only answer has been "give up and reinstall" which might solve the problem but would not help me understand why the problem happened.
I understand that reinstalling would fix all sorts of things. I understand that I manage to find some pretty weird ways to break my system. However what I really want to know is what the true problem is. I want to fix it myself for two reasons.
- I want to learn.
- This isn't Windows.
I know it's broken, I figured that out; what I want to learn is what is broken and why (and what I did wrong so I can know better next time).
I can't help but feel that answers such as "reinstall and don't worry about it" do not fit with the goal of compiling a solid resource of domain specific knowledge. I appreciate that reinstalling can be a reasonable cure-all and alternative solution if someone is in a hurry but I'd like to know how to seek more specific answers.
I worry that either I am asking less than optimal questions or I just have a knack for breaking the most obscure possible parts of my system. If my question is very obscure and no one really knows, I am fine with being told that.
I've put off saying anything because I am aware that the experts who are able to answer my questions know a lot more than I do and, frankly, I don't want to sound ungrateful. There is always a chance that my communication is less than ideal and that is no-one's fault but mine.
What is the best way to ask questions such that I can clearly indicate that I have no intention of giving up and reinstalling but really want to understand the problem (and then fix it)? And, if I do get such an answer in the future, what would be the best and most friendly way to say "thanks, but that's not what I was asking"?
chmodcommand!", is very reproducible. And sometimes the consequences are fixable without resorting to reinstall. It depends on the exact command