On 05/26/2015 02:30 AM, Per Jessen wrote:
I don't use YaST much for network configs, I tend to edit /etc/sysconfig/network/* directly. YMMV.
I suspect that the 80% case that such tools and the limited view that things like yast presents (when compared to using the CLI and as you say editing the config files directly ( http://imgs.xkcd.com/comics/real_programmers.png I'll settle for VIM, thank you kindly :-) ) get past the constraints that the GUI designers force on us. If you're happy with those constraints then fine, but so many of the threads here on this forum seem to be in that 20% of cases that the GUI designers never conceived of or variants such as * The GUI gives a "There's been an error" popup but doesn't tell you what the erro was or what caused it or what you can do about it. heck, they don't even say RTFM any more! * "retry, continue, abort" is unhelpful since it tells you nothing about the consequences. Does "Abort" clean up the files or leave them dangling half completed? What if you just shut down that prompt window or kill the process? What results from continuing after an error? I admit that running from the CLI may require a "-v" or "-vvvvvvvv" and you have to be able to interpret that the writer chose (see arguments above) or failed to chose as informative output. Perhaps it only reflected the problems he encountered while debugging, but that too tells you a lot! See http://xkcd.com/1319/ Of course many problems on this forum are really "RTFM' or "GoGoggle" class problems: http://imgs.xkcd.com/comics/manuals.png :-) http://imgs.xkcd.com/comics/devotion_to_duty.png -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org