Chris Rowland said:
Every single distribution I"ve tried has forced me into the terminal far too soon and often – Ubuntu, Debian, Fedora, Puppy.
It may be possible to use a pre-configured system without using a terminal but I don"t think it"s possible to set one up. If you ask for help you get told about terminal commands for everything that"s not trivial.
I would actually have recommended those, so I"m afraid I can"t help much, I guess… My apologies for being unable to do so.
I"ve set several of them up and have never had to use a terminal by force (I don"t think my parents, who chose Kubuntu and then later chose to switch to Fedora when a new machine had some odd hardware that wouldn"t work with the former, would even know what one was – they"ve never had to use one, either, and they set up their own OSes when they chose to switch to Linux). In fact, that"s one of the reasons I like to use Linux – in my experience, it"s usually just set-and-forget, and sometimes a bit more so than Mac OS X. (Microsoft Windows, on the other hand, I always had enormous problems of various sorts with, which is why I stopped using it. This isn"t a bash, and I hope you don"t take it as one – it simply did not work for me, and I always found it very counterintuitive even during the times when I did use it.)
Funny how that goes, I guess… I"m just grateful that the options are available so that I was able to find an OS that I found suitable.
If I might explain why people often give terminal commands, though: It"s much easier to be certain of what a user is doing, this way, because you can say "Copy and paste this and hit enter.". Some folks do forget to explain what the commands do, though, which is a problem and something folks need to learn to avoid. I cannot stress this enough – there is nothing wrong with providing someone with terminal commands, but not telling them what they do is what makes it hard to understand, and it won't help them to learn where things have gone wrong, and what to do in the future.
Giving a few terminal commands is a lot easier and infinitely quicker than telling someone "Click this and that, wait. Then click such and such. Do you see the Holy Foo on this page of the dialogue window?" and so on and on and on and on and on (which is something I"ve regularly had to do to help the few folks I know who aren"t using Linux or Mac OS X), because their perceptions of what to click and what they should be doing may differ from what yours are, or from what they"re being told (and let"s not even get started on spending hours going through GUIs with folks who thought it was alright to skip certain parts and then not tell you! Haha… Good times…), and so on…
We are here to make the Raspberry Pi work – and work well. Using other systems to compare ideas and approaches seems fine but starting threads purely to bash another product doesn"t seem right to me.
I didn"t take this thread as a bash at all – it seems, from the parent-post, to be a heads-up about a critical problem with Microsoft Windows, and intended to warn users of it to patch it if they haven"t already…