Slashdot Mirror


GrokDoc Goes Live; All GNU/Linux Newbies Welcome

An anonymous reader writes "Writing at LinuxWorld, Groklaw's PJ asks "What Do Newbies Need to Make the Switch to GNU/Linux? and invites the world - literally - to help with answering the question, by participating in the wiki she and some colleagues have just launched. GrokDoc aims to turn the usual process on its head: "Instead of experts telling newbies how to do things, we will let newbies show and tell us what they need." Might be a fantastic way to help push Linux still further toward that fabled tipping-point."

123 of 504 comments (clear)

  1. Online docs are a good thing... by mahdi13 · · Score: 5, Funny

    but you know the newbies STILL won't RTFM

    --
    "Some things have to be believed to be seen." - Ralph Hodgson
    1. Re:Online docs are a good thing... by Anonymous Coward · · Score: 5, Insightful

      Maybe the problem is newbies not knowing what RTFM means when you tell them to RTFM?

    2. Re:Online docs are a good thing... by Anonymous Coward · · Score: 2, Insightful
      Maybe the problem is newbies not knowing what RTFM means when you tell them to RTFM?
      There is a wonderful tool available called Google that answers that very question!
    3. Re:Online docs are a good thing... by Len+Budney · · Score: 5, Funny
      but you know the newbies STILL won't RTFM

      Is that the issue? I didn't read the article...

    4. Re:Online docs are a good thing... by dasmegabyte · · Score: 2, Funny

      That's because the first response to every posting is "STFU N00B."

      --
      Hey freaks: now you're ju
    5. Re:Online docs are a good thing... by bl8n8r · · Score: 2, Insightful

      That's cuz many dont know where to find the FM. Check out comp.lang.perl and see how many newbies are educated via egomaniac-with-flamethrower daily. There are indeed many too lazy to read, but you can't assume every newbie KNOWS there is a manual, and where to find it.

      --
      boycott slashdot February 10th - 17th check out: altSlashdot.org
    6. Re:Online docs are a good thing... by Stonent1 · · Score: 2, Funny

      You can leada newb to docs, but you can't make them read.

    7. Re:Online docs are a good thing... by Piobaire · · Score: 2, Insightful

      I am pretty good at RTFMs, but it seems most manuals are written with the assumption that the reader already knows the subject and just needs a reference. I recently implemented a mail system that required integrating fetchmail, postfix, cyrus imap and several other technologies. I'm no dummy, but the manuals made my head spin. I did learn the programs, but I was really annoyed with sharp RTFM comments for things assumed obvious, but really weren't. I am now helping others through the same process, from the perspective of knowing just how confusing the technology is.

    8. Re:Online docs are a good thing... by Red+Alastor · · Score: 2

      Worse is newbies (and average computer) users not knowing how to read at all. How often did you saw people just clicking the Ok button every single time a windows popup without ever reading it ?

      --
      Slashdot anagrams to "Sad Sloth"
  2. Montessori Linux by nightsweat · · Score: 4, Interesting

    This is the Montessori method of teaching Linux. Brilliant. Maybe I can get some questions I've had answered, finally.

    --

    the major advances in civilization are processes which all but wreck the societies in which they occur - A.N. White
  3. SSDD by Anonymous Coward · · Score: 4, Insightful

    Isn't this just like a regular forum like

    www.linuxquestions.org
    or
    www.mandrakeusers.or g
    or
    whatever fedora people use?

    Its just a fancy forum! Move along, nothing to see here people.

    1. Re:SSDD by bradkittenbrink · · Score: 4, Funny

      you must be new here, PJ did it, so of course it's important!!!

    2. Re:SSDD by Anonymous Coward · · Score: 5, Funny
      whatever fedora people use?
      We tend to rely on the power of prayer.
    3. Re:SSDD by An+Onerous+Coward · · Score: 2, Informative

      Actually, it sounds more like wiki.linuxquestions.org, which I've contributed to from time to time.

      Yeah, this does sound like it's reinventing the wheel.

      --

      You want the truthiness? You can't handle the truthiness!

  4. Listening to Newbies by wambaugh · · Score: 5, Interesting

    On the other hand, rather than pushing linux past a "tipping point," listening to newbies might lead to many of the aspects of the Microsoft/Mac models that many hard core PC users hate.

    Not that I think this is a bad thing, but it's worth considering that if, for instance, standardarized application appearance/performance becomes more important, much of the speed and robustness of Linux may fall by the wayside.

    1. Re:Listening to Newbies by John+Hurliman · · Score: 5, Interesting

      I'm not pointing out the obvious to troll, but remember Linux is just a kernel. If one desktop team decides to make an Apple clone that sacrifices top performance for a common user interface (I don't see how that argument makes any sense at all, but I'll go with it), another team will step up to give you the bare bones written in optimized C and assembly. People have this vision of every Linux enthusiast on the planet except for themselves heading in one unified direction that isn't to their liking; I don't think you'll see that happen any time soon.

    2. Re:Listening to Newbies by Tranzig · · Score: 2, Insightful

      Zealots don't hate an OS because it's inferior. They hate it because it's other than their beloved OS. I guess you have noticed already that Linux zealots like only the distribution they use and say that it's the only good OS, every other distributions suck.
      I think it's rather about pride. If one can't do something with Windows, he says Windows sucks and won't even try to solve the problem. If he's having trouble with Linux he says Linux is a great system but I still need to learn more about it, and probably also makes a joke about the lameness of Windows.

      If Linux doesn't take the way of standardization then another OS will and Linux will never get widespread. But when every newbie can use it, it will be a shame for having problems with Linux, as it is with Windows now.

    3. Re:Listening to Newbies by Moraelin · · Score: 4, Insightful

      It's worth pointing out though, that being user-friendly didn't stop Windows from actually being faster than X in a lot of tasks. E.g., repainting a Window works orders of magnitude faster under Windows, while in XFree86 you end up needing such silly tricks as processing only each n'th repaint when the user is resizing a window. Doubly so when the Linux equivalent reinvents the bloated wheel, e.g., by insisting to do its very own font rendering and themed widgets.

      E.g., MS Visual C still optimizes a LOT better than GCC.

      I know it will sound like blasphemy to a lot of the /. crowd, but MS really isn't a company of idiots who are just drooling over the prospect of coloured buttons. It's what you get when you cross (in more than one way;) a whole lot of hackers, with a whole lot of hard working usability experts.

      Most of Microsofts's faults, such as never thinking twice about ignoring the standards if it can optimize better without them, or inventing its own formats, are the exact same things we admire in the archetipal idea of a hacker. (The one illustrated in the Jargon file, for example.)

      And indeed it has committed more sins in the name of speed, than for all other reasons combined. (Anti-competitive behaviour included.) E.g., that's the reason why MSVC++ was always slightly deviating from the ANSI standard: they could optimize code better that way. E.g., that's the reason it let drivers run in kernel mode, and made Windows inherently unstable. E.g., deliberately pissing off Sun aside, all the changes they did to their implementation of Java were precisely aimed at making it very very fast. Etc.

      So either way, what I'm trying to say is: "user-friendly" doesn't _have_ to mean "slower than a snail". Windows has managed to stay pretty fast (fast enough to play real time 3D games, for example) even while cattering to the newbies. I'm sure Linux will, too.

      Now stability, that's another thing. No idea there, and indeed MS doesn't exactly come to mind as a good example there ;)

      Plus, as was already said, it's not like anyone will stop you from running another desktop environment, if the newbie-inspired one gets too user-friendly for your taste. E.g., most distros ship with KDE, which is aimed at precisely that: looking like Windows to newbies, yet I happily run XFce 4 instead. A couple of co-workers run Ratpoison, and that's as far from Windows (or user friendly) as you can get in a graphics mode.

      --
      A polar bear is a cartesian bear after a coordinate transform.
    4. Re:Listening to Newbies by dasmegabyte · · Score: 3, Insightful

      Which is precisely why the "Linux Desktop" market is so hard to expand -- there is no "Linux Desktop," only "A bunch of programs that LOOK like a Desktop that run under a Linux kernel." The Linux underneath may be the same or similar, but the programs on top are VASTLY different. And yet, they are consistantly grouped together as "Linux Desktop," when "Linux desktop" makes about as much sense as "Goodyear SUV."

      This is something everybody should really make a point of...because really, all of Linux' benefits start to fall apart when they hit the desktop, and one of the reasons for this is that people treat the entire set of x servers, window managers, graphics toolkits and desktop packages as "Desktop Linux," when really each is not interchangable with the others. Understand wheat I'm saying? Your machine can use any of a half dozen different mail clients and they're all compatible with each other...but the thing the user uses most, the desktop interface, has no real coherent interoperability save that offered by the ancient and useless X.

      X is no longer "good enough." Linux NEEDS something new and universal that is built for new technology, instead of patched to allow it. It's 2000-friggin-4. Let's follow Apple's lead and push the desktop onto the graphics card. Let's follow Be's lead and make the GUI something integral to the system, AS important as the CLI, and not just a "front end" for CLI commands. Let's follow -- gasp -- Microsoft's lead and not immediately assume everybody's RTFM...change defaults to prevent ignorance from killing a system and start failing over with useful error messages.

      --
      Hey freaks: now you're ju
    5. Re:Listening to Newbies by dave420 · · Score: 2, Interesting

      Maybe this is part of the problem. If there was a standard linux kernel, and a standard linux GUI, there would be a standard linux for people to move to. As there is, there are currently hundreds of variations to use. Of course people aren't going to give up their windows boxes (after you've learned one windows app, you've learned 'em all) for something that's going to act completely unpredictably across the board. It's simply too much to ask of someone who just wants to use their computers for pr0n.

    6. Re:Listening to Newbies by dasmegabyte · · Score: 2, Insightful

      No, it doesn't prove a damned thing. YOU wouldn't have to use it, any more than you have to compile iptables into your kernel. And there's no reason why it should use more overhead than, say, PERL.

      Your fear of adding new things is typical among Linux users. They can be added, but if optimizing for them requires modifications to ANYTHING else, opt to slow them down. And so we're stuck trying to patch holes in X. Fuck that, man, I'll stick with Windows...or better still, OS X.

      --
      Hey freaks: now you're ju
    7. Re:Listening to Newbies by bogado · · Score: 2, Insightful

      I am not sure about what kind of people, people that are used to the unix world can make this separation just fine. After all it is probably that they have already seen the same GNU tools working in another OS like solaris or something. Heck I even saw bash and other working under windows...

      On the other hand, people that are used to windows or macs will tend not to understand this issue, after all MS is actively tring to blur the line between the OS Kernel and the UI on top of it, even in the development model (moving gui functions to kernel to speed up NT, for instance).

      Apple I am not sure what position it has, but at least seems that they do separate UI from OS. Isn't it true that the OSX UI has a separate name "aqua" or this describe another thing compleatly? But since many user don't experience the separation it may be also hard to understand it.

      --
      []'s Victor Bogado da Silva Lins

      ^[:wq

    8. Re:Listening to Newbies by kfg · · Score: 2, Insightful

      That OSS offers something different because you CAN contribute to it

      Yes, which is why it will always be moving in 1001 different directions at the same time.

      I mean, that's really the only reason TO use Linux.

      Well, no. The fact that it can be obtained with no financial outlay is quite relevant, despite the shouts of "free as in speach," as is the fact that it is free of license encumberance if you never add a line to it.

      The fact that it's Unix may also be quite relevant because. . .

      It's not like it's a more robust product that offers fewer time wasting hassles.

      . . .this is a relative statement, not an abosolute, depending entirely on who you are, what you do with it, and how you go about doing it.

      KFG

    9. Re:Listening to Newbies by mangu · · Score: 2, Insightful
      they use are REALLY a GNU/Linux package


      Actually, what most newbies use is some sort of X/Linux, either a KDE/Linux package or a GNOME/Linux package. For instance, take some of the most popular activities for newbies in a computer: surfing the web and listening to music. Their personal contact is with the browser, let's say konqueror, mp3 player, XMMS for instance, and the desktop, KDE in this case. If there are any GNU software in there it's buried deep out of the user's view. "Linux" is a good name for it all, it's recognizable and characteristic. And, even if specific distributions have their own quirks, getting help on running those applications on other distros is frequently useful as well.

      So, to answer your first point, no I don't understand "Linux" as being merely a kernel. I do understand that GNU is just a set of software tools used in Linux. I even use some of those tools from time to time. But, in my vision, "Linux" is the overall name of the system. Naming all the different parts of a complex system is impossible for normal use. I think the GNU team tried to create an operating system, the Hurd. They never got it to be really practical. They should be glad that Linus created Linux, because it got so many people using the GNU tools, so many contributors. So, let's keep the names straight. GNU is the name of one set of utilities in Linux. It's not the name of the OS, it's not the name of the GUI, it's not the name of most of the applications.


      I personally dont feel Unix on a desktop, in the form of GNU/Linux will EVER appeal to a desktop, average joe, home user. That will come when someone actually takes the Linux kernel and actually makes something ELSE from it.


      Actually, the current status of Linux is quite close to the "average joe" system. The main problem at this time is configuration. When someone gets a good, reliable, nice and simple, configuration software, Linux will "take over the world". The only problem I see with the way Linux is evolving right now is that developers don't give too much thought at the configuration problem. They create completely new software, which throws away the old configuration.


      For instance, I had inet, and then came xinet. Despite being a rather advanced Linux user, I have never adopted xinet. I have inet well configured and, if xinet doesn't come in transparently, able to understand my old configuration files and start working without my intervention, I want nothing to do with xinet. The same is true of many other softwares. LPD vs Cups, OSS vs Alsa are two examples. To sum it up, I think the only thing lacking in Linux is a coherent and reliable configuration system.

  5. Soundcard / Printer Support by John+Hurliman · · Score: 5, Insightful

    Being able to detect and have control panels for common peripherals like sound cards and printers. Some distributions do this better than others, but a newbie shouldn't have to deal with the nuances of OSS vs. ALSA vs. JACK or CUPS vs. LPR just to listen to music and print a document.

  6. So are you saying... by Mz6 · · Score: 4, Funny

    ... that the entire /. community is a bunch of newbies?

    --
    Hmmm.
    1. Re:So are you saying... by Orgazmus · · Score: 2, Funny

      Slashdot is 750k+ members now?
      Its not very far fethed to say that we.. erm.. they are among that crowd. ;)

      --
      The system had the verbosity of HTML combined with all the readability of compiled assembly viewed as bitmap images
    2. Re:So are you saying... by wintermute1974 · · Score: 2, Interesting

      Most of the /. community is a bunch of Windows users, running IE 6, who have thought about running Linux because they heard it was cool and/or they want to put it on their resume, but have yet to really do much other than boot up Knoppix once or twice.

      I'd like to put this to the test. Are the http logs for Slashdot available? Can we see what platforms and what browsers people are using?

    3. Re:So are you saying... by admdrew · · Score: 4, Interesting

      Though you deserve kudos for actually using that software (and I agree with you wholeheartedly with regards to hypocritical Windows users), your anti-anything-linux rant is amusing and rather silly.

      I run Windows XP Pro at home because I play games. However, I've run Red Hat 6.1, 7.1, and 8 on other machines, but have never found them to be terribly useful for personal uses. If I were to constantly have more than one machine, I would probably run Linux as well. I, however, do not have any qualms about running WinXP, especially because it *can* be a very stable and powerful OS.

      Professionally, I've done my web developing in the past with perl on a Linux server. As the years went on, however, our company made the jump to Windows 2003 Server and .NET using C#. Though I am no fan of the "corporate bastard" that is Microsoft, production costs have lowered and development has become much more efficient since we made the switch. All biases aside, I have been relatively content to use a Microsoft product in this situation.

      Free software is great, but is seldom intuitive enough for the masses. Linux, and the realm that surrounds it, is largely for those that enjoy and have the time to endlessly tweak their software. I have enormous respect for those kind of people, and I must admit that I've felt jealous of them and their coolness.

      When you call everyone "IE-using scumsuckers" and "shitbags", you're as annoying as the very n00bs you taunt. At least Linux wannabes are open to software that they don't even use.

    4. Re:So are you saying... by Thomas+Shaddack · · Score: 2, Informative
      $HTTP_USER_AGENT is unreliable; too many browsers are set to identify themselves as MSIE, either for privacy reason (more difficult to track an individual without cookies in an uniform sea of same browsers) or because some poorly designed webs have other browsers screwed up.

      If you want at least somehow reliable stats, you have to rely on something more robust, eg. passive TCP fingerprinting; a good tool for this purpose is eg. p0f.

    5. Re:So are you saying... by Kick+the+Donkey · · Score: 2, Funny
      Imagine that... A Slashdot poster browsing from work...

      Ooops! Here comes my boss!

      --
      /. is a bunch of nerds at a million typewriters. It's not a political conspiracy determined to undermine your beliefs.
    6. Re:So are you saying... by zcat_NZ · · Score: 2, Interesting


      <img src="images/not-msie.png" alt="" />
      <![endif]>

      <!--[if ie]>
      <img src="images/msie.png" alt="" />
      <![end if]-->

      And a quick grep grep of "not-msie.*MSIE" in the apache logs is quite enlightening.

      --
      455fe10422ca29c4933f95052b792ab2
  7. Simple by mrjimorg · · Score: 5, Insightful

    NEVER tell me to modify the xyz file in the abc directory!

    1. Re:Simple by Anonymous Coward · · Score: 2, Interesting

      BINGO!

      Instead of jillions of faq's and forums ... someone needs to start a project site to add GUI's for every single configurable thing that happens in linux.

      Next>Next>Finish is why Windows is 'winning'.

    2. Re:Simple by johannesg · · Score: 4, Informative
      There is a distinct overuse of the 'advanced' button in GUI's these days. You click to open a config window, and immediately click again to see _all_ the options because some asshat decided that you should initially see only three instead of all four.

      Slightly better GUI design for config windows would help a great deal. What we need:

      - make the damn windows resizable already! Especially if you want to put in a three-line selection box with 3000+ items! (this is of course a point mostly aimed at Windows).

      - Do NOT use tabs, *especially* if you need more than one row of them. Instead, use a Mozilla-style category list on the left side of the window. That allows you to group together related 'tabs', and use longer (and more descriptive) names.

      - Group options together in a logical fashion. Disable controls that are made irrelevant by other choices.

      - Provide a fscking help option for EVERYTHING, describing the finer nuances of setting or unsetting that option. Don't write "LPGR: sets the LPGR option". Describe what it is, why I want it, what happens if I set it and what happens if I do not set it. If a value is a string, provide examples and full BNF syntax.

      - Do NOT use acronyms or abbreviations unless you are REALLY certain they are common words. And even then it is probably better not to.

      - Never invert the meaning of a checkbox. Checkboxes ENABLE things. If you check them something should be turned ON, not OFF. "Disable debugging" is incorrect. "Enable debugging" (with inverted state) is. If you do it right you will find you can drop the "enable" without losing meaning.

      - While I'm on the subject anyway, checkboxes are for on/off choices. There are plenty of things that masquerade like on/off choices but really aren't (for example, the choice between 22KHz and 44KHz sound has only two options but a checkbox is utterly inappropriate since 22KHz is not the logical opposite of 44KHz even if your application only has those two options). Use radiobuttons or a combobox for those, even if there are only two options.

      - Do not hide options behind three layers of windows, tabs, subwindows, and more tabs. You are allowed one layer only. It is provided by the navigation choices in the left-hand column. This allows any user to navigate to his option of choice in ONE click.

      - Remember the last location of the user. Select it for him, next time he opens the configuration window. This will probably save another click.

      And most importantly, there is this:

      - Work with your own software. Try to _feel_ what is annoying; what works, and what doesn't. If some task is unpleasant to accomplish, redesign the GUI so it is no longer a problem.

  8. Another one? by Anonymous Coward · · Score: 3, Insightful

    No offense as I'm sure the intentions are good, but aren't there already several dozen similar sites and services like this? Why not contribute the man power and resources to an existing project instead of duplicating the work?

    1. Re:Another one? by sulli · · Score: 2, Funny
      Why not contribute the man power

      Because new users won't know to use man in the first place!

      --

      sulli
      RTFJ.
    2. Re:Another one? by dave420 · · Score: 2, Insightful

      The very fact that linux needs sites like this just to get newbies up and running speaks volumes. Don't try and cover up the symptoms, but get to the cause.

  9. Blind by codejester · · Score: 4, Insightful

    Blind leading the blind? I don't see many schools asking students to lead class and I think there is a reason...

    1. Re:Blind by jamesots · · Score: 4, Insightful

      Blind leading the blind? I don't see many schools asking students to lead class and I think there is a reason...

      However, you will see plenty of student teachers observing classes so they can learn to teach better.

      --
      Ho hum for the life of a bear
    2. Re:Blind by swv3752 · · Score: 2, Informative

      Nope. RTFA.

      Basicaly, Experienced Linux users sit a complete noob down and watch what they do.

      Imagine sitting your mother/girlfriend/neighbor down at your Linux box then record what she does to get online. Maybe she has trouble navigating the menus. Maybe there is problem just logging in. Is there any problems using the broser itself? Which web browser was chosen?

      There are more complex tasks like setting up the computer for internet access. Also one can see how well they can handle finding and reading existing documentation.

      After all this documentation is collected, then the community can design better interfaces and write better documentation.

      --
      Just a Tuna in the Sea of Life
    3. Re:Blind by tsg · · Score: 4, Insightful

      Blind leading the blind? I don't see many schools asking students to lead class and I think there is a reason...

      If you're building something for the blind to use (software, sidewalks, whatever), don't you think you ought to ask the blind what they need?

      --
      People's desire to believe they are right is much stronger than their desire to be right.
    4. Re:Blind by iabervon · · Score: 2, Insightful

      Perhaps they should, though. I was a teaching assistant for a few terms, and found that by far the best use of the TA's time (as opposed to the lecture) was answering the class's questions. I'd show up with a lot of notes, and ask the class what wasn't making sense to them. Half of the time, the material I would end up covering wasn't something I would have thought to cover, and the class found it very helpful (at least based on attendance at later classes, which weren't required).

      The teachers know the material, but only the students know what it is that the students don't know, so for a class which isn't presenting new material but rather making sure the students really know the material, it makes sense for the students to chose what will be discussed in class.

      The current educational system suffers from a lack of good feedback from the students to the teachers on what the students know, so the teacher will often continue to talk when most of the class either already understands or is lost.

  10. What newbies need... by Anonymous Coward · · Score: 5, Interesting

    1. An installation process as straightforward and simple as Windows
    2. The device compatibility offered by Windows
    3. The level of cooperation shared by Windows applications
    4. The games available on Windows
    5. The simplicity of changing system configurations offered by Windows

    I wonder where the heck I can find an OS that does all that and more? Hmmm...

    (This is not a bash on Linux. I use Linux and love Linux for doing SERIOUS WORK. Most of the world does not do SERIOUS WORK at home. Windows meets virtually every requirement a home user could have. To meet these requirements, Linux would have to effectively become Windows. I, personally, would never use that distro.)

    1. Re:What newbies need... by deadmongrel · · Score: 5, Insightful

      1. An installation process as straightforward and simple as Windows
      True. Simple installation yes. Like windows no. Why? I haven't come across a newbie who can do a clean installation with windows(I am not including those recovery disks that just dump an image into hdd). No one complains about windows because not many newbies install windows. it comes pre-installed on their system. In linux I really like the 4-click install of XandrOS.Its clean and simple and asks minimal questions.
      2. The device compatibility offered by Windows
      this is going to a problem because not all hardware manufacturers want to openup their drivers. A lot of them have given out binary only drivers(Think Nvidia) but the drivers suck.
      3. The level of cooperation shared by Windows applications
      agree.
      4. The games available on Windows
      chicken and egg problem 5. The simplicity of changing system configurations offered by Windows
      I find apple give more simplicity when it comes to changing systems. But if we narrow our vision to what both apple and MS does for usability, then we are bound to make the same mistakes. There are other designs that are much more usable than windows and apple for that matter. We just shouldn't follow windows, just because people are used to it.

    2. Re:What newbies need... by rRaminrodt · · Score: 3, Interesting

      1. Have you tried installing a distro like Mandrake versus Windows lately? I do quite a few windows installs as part of my job, and its not really that simple. I know this has been said a lot, but this is especially true when it comes time to get all those other apps like Office, IM, pcAnywhere, etc. onto the PC. Distros typcially include this step in the install, with windows everything needs to be done seperately.

      2. Many devices are compatable, but require a lot more legwork on part of the user. I agree that this stinks, but it really does depend on the companies building them to cooperate, either with driver disks or unencumbered specs.

      3. I don't get this one. Do you mean windows style IPC? If you stick with a desktop like Gnome or KDE you pretty much have interapp communication. Plus CLI applications are already able to do that with pipes.
      If you mean library reuse, most distro's packages are better at that than most windows apps. They access shared libraries and don't carry around their own copy.
      And still, even with XP and 2000, I still (occasionaly, to the developer's credit) see windows apps that stomp on each other.

      4. Given. But games will only stop one segment of the computer using population. Mom might need the Sims. But grandma just wants email and solitare.

      5. I hate configuring some things in windows now that I'm used to config files. So I'm biased. But there are tools out there to do the job. They just need to be a bit more polished. And by polish I mean useful, unlike the new XP-style control panel, which I constantly have to turn off.

      I sure hope that windows meets home users needs, otherwise there would be a lot more returned computers. But what I like most about Linux & the distros are the layering capabilities. You can do server, desktop, l33t haX0r desktop, embedded device all with the same core, by picking different layers. And they stay (mostly) compatible.

      This means a "windows easy" desktop may be inevetable, but I don't think it will arrive with much fanfare. It'll be a gradual thing, like most OSS development has been.

      --
      They'll think I've lost control again and leave it all to evolution. -- Supreme Being, Time Bandits
  11. New Users by OxygenPenguin · · Score: 2, Interesting

    Even uber-newbs like the differences they can see between Linux and other OS alternatives. What we need is something they can understand, while still maintaining the environment of speed and customization that we have all grown to love. Discovering new things should be up to the user, but for those who need their hands held, they have somewhere to go instead of resorting back to the monopoly.

    --
    Read the only personal Runyon page out there.
  12. More fluff ahead by prgrmr · · Score: 3, Funny

    as newbie after newbie complain that linux needs a "clipy". or worse, a talking, pop-up tux.

    1. Re:More fluff ahead by Unnngh! · · Score: 5, Funny

      A talking, pop-up tux that spits out hundred-page man pages might be kinda funny though...

  13. I like this idea by dumpsterKEEPER · · Score: 5, Insightful

    Assuming this is implemented well, I could see this being a very useful tool for new linux users. It seems like the hardest time I have convincing people to at least give Linux a try is when they want to know where to go when they need help. It is often a little difficult to describe to them how they need to search Google, picking through endless messageboard postings and offtopic comments, and find what they need, especially when they aren't even sure what they were looking for in the first place. A centralized resource that is helpful and friendly could be very useful for those who are intimidated by learning a new OS.

  14. Sounds Like a Plan by fiftyvolts · · Score: 4, Interesting

    This kind of testing is exactly what needs to be done. Recently I took several seminars on useability engineering and useability testing, and I was amazed at how much better you can make a product after testing it. I suggest that if you do plan to add your input to the project that you incoiurage the user to think out loud and write down all the things they say. It's really enlightening to hear a user say something like, "I'm looking for a button to do XYZ." when you know that the feature he wants is in a menu right in front of him.

    My only concern is that, quite frankly, I find that the first and most difficult hurdle for new users is installing linux. Many people have no clue what's inside of their machine, and more times than not you need to specify some odd bit of hardware during the setup process.

    Heh, I should try this on my mother.

  15. How about this? by kensai · · Score: 4, Insightful

    Stop calling them newbies. It's to much of a deragatory name and tends to push people away. How about calling them beginners or something like that?

    1. Re:How about this? by tsg · · Score: 3, Interesting

      Stop calling them newbies. It's to much of a deragatory name and tends to push people away. How about calling them beginners or something like that?

      Because the problem is not the name, it's that it's used in a derogatory fashion. As soon as the new name becomes politically correct, the people who use "newbie" to belittle them will use the new name to belittle them. Changing the name will not stop people from being derogatory to whom it refers.

      --
      People's desire to believe they are right is much stronger than their desire to be right.
  16. I Disagree by Seek_1 · · Score: 5, Interesting

    I don't consider myself a newbie by any stretch of the imagination, but the majority of the time I still can't make sense out of linux documentation.

    I tried every night for two straight weeks (reading the docs, getting some great help from the standard linux forums, reading every samba tutorial I could find etc) to get Samba working on my home network before finally giving up on it (and hence linux altogether).

    You can't really complain about newbies not reading the manual when the manual either just plain doesn't contain the information you need, or has wrong or out-of-date information in it.

    1. Re:I Disagree by Elecore · · Score: 5, Informative

      I've gone through a few different distros the past year, and I must say that so far, the Gentoo handbook is the best manual for linux I've ever read. They show you exactly what to type, and where, as well as telling you WHY you're typing it. I learned a lot about linux simply by installing and troubleshooting Gentoo.

    2. Re:I Disagree by koniosis · · Score: 2, Insightful

      I have to admit, a LOT of linux programs I have tried using and projects that I've seen have some of the worst documentation I;ve ever seen. Usually going something like "Do A, then B will be ready" when in fact there is so crucial step to get "B" ready that it is assumed the user will just "know". Most the time this leads to hours of IRC in some remote channel where most the people there are afk for 23 out of 24 hours.

      --
      I spent ages trying to think of sig, but never did :(
    3. Re:I Disagree by KrispyKringle · · Score: 4, Interesting
      It really depends on what you're doing. For something as mature as Samba, you should be able to get docs (and in fact you can--I know, because I've read and used them). But for some new software, the code is beta or done, but the docs have to wait. A good example of this is the 2.6 IPSec implementation. I tried to use it with ipsec-tools and easily got transport mode working, but found virtually no documentation on tunnel mode. I ultimately gave up and went with FreeBSD.

      Point is, most commercial software isn't released if it's not documented (not always the case, of course). But Open Source you get when you get it. If it's not done, it's not done but you can still download it. If it's done but the docs aren't, nobody holds the release up. C'est la vie.

    4. Re:I Disagree by Seek_1 · · Score: 4, Interesting

      Really? Well hey, if you can point me to one that'll work with both WinXP and Win2k you're more than welcome to. (Infact I'd appreciate it!)

      However, until then, my network server will remain a Windows 2000 machine, where I can actually access its files without any issues whatsoever from other machines.

    5. Re:I Disagree by Welsh+Dwarf · · Score: 4, Insightful

      When a so called 'newbie' starts out he shouldn't (need to) read documentation telling him how to use vi to edit /etc/samba/smb.conf.

      Instead he should be directed to a convenient administration tool (swat/webmin) which would allow him to set up his home server without 3 hours spent trying to make head or tail of his new (GNU/)Linux system.

      Later, if he wants to become more proficient, or fine tune his installation (in general), then by all means show him the CLI and point him in the direction of a M for him to RT, just not straight away.

      What a lot of us seem to forget all to easily is that there is something called information overload, and learning the command prompt/SysVinit runlevels/Samba configuration/hosts.Allow/Deny.... all at once is an easy way to get there. We didn't learn all of this in one weekend, so we shouldn't expect others to.

      --
      Ask 8 slackers a question, get 10 awnsers (a citation, but I can't remember from who)
    6. Re:I Disagree by chill · · Score: 2, Interesting

      And this is where something like Grokdoc would come in handy, though it doesn't cover Samba.

      What distro were you using? Where did you have problems? Were you trying to just share stuff or do full Domain Authentication as well?

      I just installed SuSE 9.1 on a latop here at work, and it saw all three NT/2K domains immediately. I was able to share some files just with a couple of clicks.

      -Charles

      --
      Learning HOW to think is more important than learning WHAT to think.
    7. Re:I Disagree by koniosis · · Score: 4, Insightful

      This is the attitude that causes so many problems for new users to Linux. People assume that the exsisting documentation and HOWTOs are fine because they understand them and can set up the thing in question without a problem. You are not listening to a REAL user who has REAL problems. This is the aim of this project, to get away from the notion that just because some document already explains it, that is enough. It's called User Testing, and it is something that more Linux projects need to do.

      --
      I spent ages trying to think of sig, but never did :(
    8. Re:I Disagree by mahdi13 · · Score: 3, Insightful

      I agree, SAMBA is one of the largest piles of mess I've ever run across. Most of the docs available tell you TOO much, which is just confusing and causes more problems then it solves.

      When I first used SAMBA I read through the entire documentation. After the headache subsided, I only needed to look at 3 pages to configure it. Then I used SWAT and had to reconfigure it afterwards since it messed it all up.

      I currently have a SAMBA server running on Fedora Core 1, works great with very little trouble using the GUI to select the shares and permissions. Even have my printer setup through it, works great.

      The thing with SAMBA is, once you have it working...don't mess with it!

      --
      "Some things have to be believed to be seen." - Ralph Hodgson
    9. Re:I Disagree by JohnTheFisherman · · Score: 4, Insightful

      I think I finally got a config file working, and it was a tremendous pain in the ass. I've been using Linux for years, though I usually mostly stick with Windows for some strange reason. Oh....like for Samba. It's very difficult to read through a variety of articles, with 400 different ways to do it, some several years old, all of them conflicting, and virtually none of them well explained. I'm sure it gets old answering newbie questions, and believe me, it comes through in most any answer how tired the 'expert' is.

      Even when I set up the share, which finally worked pretty well in Windows, I still can't use it correctly while mounting it in another Linux box. I suppose I still might have something misconfigured, but it keeps telling me the owner is '502,' which is the ID# (user #? whatever you call it) of the actual owner, but not the name of the owner. It sorta works, but not for subdirectories where I still lose ownership of what is supposed to be a full control subdir and files. It's just too much hassle, and I think somethings broken based on how it identifies the owner and permissions. Back to Windows. Hey, everything works. *shrug*

    10. Re:I Disagree by kfg · · Score: 5, Insightful

      It really depends on what you're doing. For something as mature as Samba, you should be able to get docs. . .

      He didn't say he couldn't find docs. He explictly said he found lots of docs.

      Finding docs is worthless if they all suck.

      In my early Linux days I floundered around for a couple weeks just trying to find basic information. I'm no command line novice either, going back to the days when we typed it, on a typewriter. Finally a simple diagram of the generic file system printed in Linux Journal (that's right, even Linux for Dummies didn't bother to even show me a diagram of the file system, and this is enough editions back that it was still command line centric) and a copy of Kernighan and Pike had me whizzing along in about half an hour.

      Because Kernighan and Pike writing generically decades ago wrote better Linux documentation than what was available for Linux, and even better Red Hat documentation than that which came with my boxed set with triple the page count. I would have been better off if Red Hat had just tossed me a copy of TUPE with a note on saying,"Best we can do, you'll have to figure the rest out by yourself."

      Because Kernighan and Pike know how to write documentation.

      KFG

    11. Re:I Disagree by CAIMLAS · · Score: 2, Insightful

      That's contradictive. If you've given up on linux, you are a newbie. Just because you know windows does not mean you're hot shit in the Linux world of knowledge. They're knowledge sets that are not mutually exchangeable.

      Samba configuration is exceedingly simple.Most distros even come with a very thorough config template made out for you. You can get it set up and running in a matter of seconds:

      [global]
      netbios name = machine
      workgroup = name
      security = share
      [shares]
      path = /shares
      browseable = yes
      wide links = yes
      guest ok = yes

      That's all you need for basic functionality. Probably more than could be gotten by with. To add insult to injury, there are dozens of tools to do more advanced configuration for you. Are you sure you were reading the correct documentation?

      --
      ~/ssh slashdot.org ssh: connect to host slashdot.org port 22: too many beers
    12. Re:I Disagree by poot_rootbeer · · Score: 2, Insightful


      Yes Mark, you're right. Documentation QUANTITY for Samba under Linux is high, therefore documentation QUALITY must be impeccable.

      Come ON.

      In fact, the more different versions of the documentation there are, the worse it is to try to follow them. How do you know which version is the best? How do you know which versions are even CORRECT?

      Look, you can cop your RTFM/PEBKAC attitude all you want, just stay away from the newbies, ok? You're not doing anyone any favors otherwise.

    13. Re:I Disagree by debian4life · · Score: 3, Funny

      Welcome to Slashdot. A nice friendly community where you can bash Microsoft and talk about the wonders of Linux and Open Source Software.

      Just don't ask for help on because you will be called stupid and ridiculed for wasting everyone's time.

      That is always my favorite troubleshooting answer.

      "It works fine for me, I don't know what your problem is?"

    14. Re:I Disagree by ostrich2 · · Score: 2, Informative

      For interested parties, it's PBCAK, not PEBKAC. It stands for "Problem between chair and keyboard." (It mean's user error.)

    15. Re:I Disagree by Lumpy · · Score: 3, Insightful

      When a so called 'newbie' starts out he shouldn't (need to) read documentation telling him how to use vi to edit /etc/samba/smb.conf.


      Huh?? why is anyone new using anything but the gnomeedit or other point and click text editors that are automatically installed?? It's just like the windows ones they are comfortable with...

      And anyways, why are you messing with the smb.conf file or SWAT?? use the mandrake config tools and call it done. Too many newbies are being directed at advanced distros like gentoo and Debian and Slackware.... Give them the easiest for anyone to use, Mandrake 10.0 and soon to be even easier SuSE.

      That was the biggest problem in my Local LUG.. the Seasoned Linux experts are telling newbies... "dont use XXXX use Gentoo it's better... here Debian Stable is what you want, etc....etc....etc...

      Most linux newboes need to start with Knoppix then graduate to a real-installer but still brain-dead easy to use like Mandrake then graduate when they learn to hate RPM based distros...

      throwing someone the Linux from Scratch PDF when they are a newbie is plain stupid, and most linux experts pull that crap on newbies every single day.

      Getting them to change is the first step... the LUG I help with is standardized on Mandrake for newbies... we also reccomend that they actually BUY it so they can access the support community for it. then after they are ready they graduate to other distros...

      --
      Do not look at laser with remaining good eye.
    16. Re:I Disagree by eugene+ts+wong · · Score: 2, Interesting

      I agree with you. I'm amazed @ how Eric Raymond [or was it somebody else?] who had trouble configuring his printer with CUPS, which should have been automated. Are we really going to say that Eric didn't try enough or that he didn't have enough experience with the command line? Linux users seem to have such difficulty in admitting that Linux is user hostile despite compelling evidence.

    17. Re:I Disagree by moosesocks · · Score: 2, Informative

      I wholehartedly agree with you 100% here.

      Funny thing is that Gentoo's documentation has been criticized by the 'hardcore' linux community.

      It's consistent, it's up to date, and most of all, it's really easy to read. Like the parent mentioned, you really do learn a lot when reading it.

      Gentoo is without a dobut one of the most complicated of the distros. Consequently, it is one of the most difficult to use, and even long-time linux users will need to refer to the documentation.

      As a result, the documentation was under a lot of scruitny, and the Gentoo community saw that it needed to be improved and worked on. As a result, the hardest distro to use has the easiest documentation.

      Honestly, I'd wager that because of the excellent documentation, Gentoo is one of the best/easiest linux distros.

      I should note that Gentoo's DIY approach is NOT fit for the masses. Even with the excellent documentation, most users will be frightened out of partitioning their drives manually with fdisk.

      Even so, when I have to use linux, I go to gentoo. It's nice that it's fast. The community is excellent, and without a dobut, has the best documentation. If you have a problem, IT WILL BE solved by either the documentation or (as a last resort), the forums (which are also the best among the linux community.)

      That being said, Gentoo's far from perfect. As a distro, it's excellent. But it's still Linux, and still has all of its flaws. (Why oh why can't they ditch the standard driectory structure?).

      For now, I'm using OS X. It's fine for my needs, and largely self-eplanitory. The official documentation, however, is way below par. Microsoft's knowledge base (though highly redundant and bloated) beats out Apple's.

      --
      -- If you try to fail and succeed, which have you done? - Uli's moose
    18. Re:I Disagree by RAMMS+EIN · · Score: 5, Informative

      I agree with that. At the time I installed Gentoo, a lot of UNIX commands were still abracadabra to me. Still, I managed to get Gentoo up and running without a hitch, and learned a lot in the process. What this means is that Gentoo, typically considered for advanced users, is a good way to kickstart newbies.

      I really think that, in general, one of the best ways to learn about computers (any part of hardware and software) is by diving into it at the deepest level with a good walktrough. This not only teaches you how to do things, but also why you do them that way. With strong knowledge of the low level, it is easy to come up with any solution for the high level.

      Of course, the _quickest_ way to learn how to use a computer is to learn just the things you need to use. However, do not confuse this with the easiest way. For example, there is a widespread belief that GUIs are more intuitive, and therefore easier to use than the command line. I disagree. I can hardly think of anything more intuitive than pressing the key which has the character that you want on the screen. From there on, you build up the complexity until you have a command that does what you want done, and press the key that causes the command to be executed.

      In a GUI, one typically moves the mouse (in a different plane!), to the location where an action is to be performed, then does one of clicking, right clicking, holding a key and clicking, double clicking, etc. Often, the command to be performed is selected from a menu, which sometimes appears in a completely different location from where the action is performed. Intuitive?

      The strength of GUIs is that they are discoverable. Once you learn how to move the mouse, select items, and navigate menus, you can discover pretty much everything a program can do by doing just that. There is a lesson here for CLI designers: make your interfaces discoverable. Tell the user how to get a list of commands and how to find out what they do.

      --
      Please correct me if I got my facts wrong.
    19. Re:I Disagree by Welsh+Dwarf · · Score: 2, Informative

      And anyways, why are you messing with the smb.conf file or SWAT?? use the mandrake config tools and call it done. Too many newbies are being directed at advanced distros like gentoo and Debian and Slackware.... Give them the easiest for anyone to use, Mandrake 10.0 and soon to be even easier SuSE.

      That's exactly my point (sorry for the SWAT reference, being predominantly Slackware myself, I don't really know what's out there).

      But what's really needed is for people to be sent to the right tool for the job for them, as in, not the right tool for the job for joe h4x0r.

      If home users can use linux without having to become a sysadmin, or have one tell them how useless they are, then the biggest problem with Linux on the desktop is dealt with.

      It isn't even a technical problem any more, the solutions exist, we just need to point them to them.

      P.S: Too all those who are complaining about an easy to use distro being just another Windows, may I remind you that what runs on one distro will run on another, and the bigger the market share, the more lickley we are to get the hardware support/games/Tax applications that everyone here is calling for.

      --
      Ask 8 slackers a question, get 10 awnsers (a citation, but I can't remember from who)
    20. Re:I Disagree by mrroach · · Score: 5, Informative
      OK, I call shenanigans on all of you. You're putting me on, right?

      You did not even read this documentation that you are claiming is no good.

      You also did not look for it very hard.

      Let's see...
      • go to samba.org
      • click on USA
      • click on documentation
      • choose the html version of the howto guide (the first link on that page)
      • skim through the index and see "2. Fast Start: Cure for Impatience" and click it
      • Lo and behold, the two configurations you just mentioned are configurations #1 and #2 on that page.


      Now, have a look at that documentation, then come back and tell me that it sucks and why, or tell me that it doesn't but that you just couldn't find it, or tell me that you were really just not looking that hard.

      -Mark
    21. Re:I Disagree by mrroach · · Score: 2, Insightful

      I don't know why I am even bothering.

      First point: I help newbies all the time. I do everything I can to help on mailing lists and writing documentation myself.

      Second point: This is not about me helping a newbie. This is the newbie saying "Samba documentation is bad" Now, since I have personally looked at the samba documentation a number of times and found it to be quite good, I found this interesting. I went looking for documentation and found not only quantity, but quality and that it was very easy to find (there are lots of products that aren't, I am very happy to admit that).

      If I'm correct, and it is high quality, then the rest of the statement follows, correct? So the crux of the issue is whether samba docs are good or no.

      So far, no one has said, "Mark: take another look at that documentation, see where it says 'do xyz? There's no way a normal human will understand that."

      Instead the blanket statement has been made, and it's supposed to be obvious that this is Bad Documentation.

      I say the documentation is Good Documentation and have pointed to very specific useful areas, the only line of discussion I am interested in pursuing is one regarding why this is Bad Documentation.

      If I am wrong, and this truly is Bad Documentation, I will recant my statement that PEBKAC.

      Good grief

      -Mark

    22. Re:I Disagree by nolife · · Score: 2, Interesting

      I've been running Samba in one form or another since 1995-1996. It was much easier to get help back then as Samba was limited in functionality and the only popular clients were DOS and W3.11. Luckily I learned the basics of Samba then as now the documentation is almost a nightmare. Samba offers at least 5 different methods of authentication and depending on what MS OS and service pack or KB fixes you have installed, things may operate differently. Roaming profiles? Domain logins? Using AD for account creation on the Samba machines? The list goes on and on. I would say the "poor" documentation comes from the success and confurability of Samba.

      --
      Bad boys rape our young girls but Violet gives willingly.
  17. Newbies don't need Linux... by Anonymous Coward · · Score: 5, Insightful

    The same way they don't need DOS. And they definitely don't need "GNU/Linux". Give us a break, any newbie who wants to go around pronouncing that awful name all day is a nerdy geek and no newbie.

    Anyway, Linux is the underlying OS and no use to any newbie. Newbies want to use a user-friendly desktop system. The discussion can't be centered on Linux itself. There should be discussions specific to each distro or window-manager.

    Newbies don't give a shit about the OS. They want to install a desktop and run things and go back and easily find and use the files they created last week. Oh and, no childish games about names, evil monopolies, litigious bastards and whatnot. In other words, no "grokxxx"!

  18. WM? by zogger · · Score: 3, Insightful

    What manual? You mean man pages (already getting into an abbreviation now, just the name) written in programmer/sysadmin speak, which is composed of equal parts arcane jargon and acronyms, and assumes a background in Unix administration and total familiarity with running Bash? That manual? You are correct, they will look at it and go "this is absolutely NFG for my purposes right now".

    1. Re:WM? by stevey · · Score: 5, Informative

      You can do far worse than pointing people at The Linux Cookbook.

      This is something that is task orientated which seems to make lots of newcomers to Linux (but not computers)

  19. What Do Newbies Need to Make the Switch to Linux? by no_such_user · · Score: 3, Insightful

    Patience.

  20. Whos should switch and who shouldn't by erroneus · · Score: 3, Insightful

    To determine who should switch, it is important to note where Linux is best/strongest and where it is most weak.

    We still can't run games out of the box. We've got to compile kernels and tweak and adjust because I have YET to see a Linux distro install itself optimized for any given graphics card allowing for 3D acceleration that's worth a damn... OUT OF THE BOX... (please don't tell me anything that works after tweaking... it's the before-skilled-tweaking that I'm talking about.)

    So gamers? You're stuck with the trojan/virus/worm-target, MS Windows for now.

    If you're browsing the web and doing email and quite possibly even things like the office apps, graphic and web design, you're about ready with some exceptions. Just install whatever Linux distro appeals most to you and go with it... they're almost all free to acquire to take your time, learn a little and install them all, evaluate and decide. It's all good.

    If you're running server-oriented services such as SQL, HTTPd, SMB, NFS, FTP, SMTP, etc... Why haven't you changed already!? What are you stupid?!

    1. Re:Whos should switch and who shouldn't by dasmegabyte · · Score: 2, Insightful

      People like to mention Linux as a solution for the virus-ridden Windows products. This is of course a very FUD non-solution that effectively creates more work for the user with less potential and no address of the real issue.

      I mean, think about it. If you had to keep Windows, what's the solution to ridding yourself of virus worries? Education! Learn what to trust, what not to trust. Learn how to lock down your computer. And learn how to find out about new viruses.

      Now, if you want to use Linux, what's the first thing you need? Education! A lot more education than simply learning to use Windows Update. And what's more: to keep your Linux install secure, you'll STILL have to educate yourself about viruses. Linux isn't immune to them, and as more people use it, there is more incentive to actively exploit security holes.

      The real problem with security isn't the software. It's lazy and ignorant administrators who treat their computers like appliances. There are many, many companies that use MS Windows for SQL, HTTPd, SMB, FTP, SMTP, etc who have NEVER had a problem and never will -- because their administrators are on the ball, willing to test new patches themselves rather than waiting weeks to see if there are complaints on the newsgroups, and basically have set their machines up in an intelligent manner. Place I used to work has 13 webservers running unpatched IIS 4. They still resisted Code Red -- because they had been set up correctly, were running all scripts in user space, weren't running random DLLs and weren't running the (largely unnecessary) indexing service.

      Runing Windows is easier than running Linux, and therefore it's easier to run it wrong. By default, all services run as the "local system" account, which is roughly equivalent to root. If you want unix-like security in windows, most of these services can be modified to run in a user context. Before I'll use a Windows 2000 box, I have to shut down at least 13 services that I don't need and that sit there, chewing up my ram. I still prefer this to the THOUSANDS of options I have to know and set on a Linux box. Knowledge may be power, but learning new syntactic and symantic bullshit is a waste of time unless the REAL problem is one of syntax.

      --
      Hey freaks: now you're ju
  21. First step by sulli · · Score: 2, Insightful
    is to stop confusing the GNUbies with the blasted "GNU/Linux" name!

    I know RMS has a point that many GNU utilities are in Linux. But as a brand name, it's crap. "Linux" is hard enough to remember or understand in comparison to names like "Macintosh" or "Windows" - please, please don't make it worse by adding something vaguely unpronounceable and obscure-sounding at the beginning and then arguing about it endlessly.

    Just call it Linux. Not Lindows, not GNU/Linux, not the endless new and old distribution names (and what the heck is "Gentoo" anyway?!), just Linux.

    Then people might understand what the heck you're talking about. Which would be a step in the right direction.

    --

    sulli
    RTFJ.
    1. Re:First step by koniosis · · Score: 2, Insightful

      The problem is that there is no "Linux" operating system, there is just the Linux kernel, which is such an un-userfriendly thing (i.e. most Windows user don't know what a kernel is). I agree that Linux needs to be a name associated with an Operating System, like Linspire (Lindows). Linspire is probably the first distribution of linux i've seen that is taking the right approach to desktop market penetration. Most people think Linux is a server thingymabaob thats too complex for them to understand (perhaps ditching Linux as a name would be a smart move? call all distros a new name LinOS)

      --
      I spent ages trying to think of sig, but never did :(
    2. Re:First step by c0rN_g0aT · · Score: 4, Insightful

      "I know RMS has a point that many GNU utilities are in Linux."

      Linux is just a kernel. Linux is in a GNU system and not the other way around. Stallman is the father of open source software and newbies should be taught this as well as just exactly what linux is. This will avoid stupid questions like "I downloaded Linux and its nothing but a 30 meg source archive for a kernel or something" If GNU/Linux is too hard for them to understand, they have no hope of ever using and maintaining a GNU/Linux system.

    3. Re:First step by tsg · · Score: 2, Insightful

      The problem is that there is no "Linux" operating system, there is just the Linux kernel,

      Not that anyone asked, but here's my $0.02 about the whole GNU/Linux thing. While it may not be the strict definition of what an operating system is, it stops being Linux if you change the kernel but keep the GNU utilities. It wouldn't stop being Linux if you change the GNU utilities but kept the kernel. The question I think needs answering is does running the GNU utilities on MacOS X make it GNU/MacOS X? How about GNU/Windows or GNU/BSD?

      --
      People's desire to believe they are right is much stronger than their desire to be right.
    4. Re:First step by The+Original+Yama · · Score: 2, Insightful
      I know RMS has a point that many GNU utilities are in Linux.
      That is not the main argument the FSF use these days. You can find many better reasons here.
    5. Re:First step by nathanh · · Score: 3, Insightful
      While it may not be the strict definition of what an operating system is, it stops being Linux if you change the kernel but keep the GNU utilities. It wouldn't stop being Linux if you change the GNU utilities but kept the kernel. The question I think needs answering is does running the GNU utilities on MacOS X make it GNU/MacOS X? How about GNU/Windows or GNU/BSD?

      It's not just about the GNU utilities. People forget that for Linux in 1991, GNU was *everything* except the kernel. The C library. The init scripts. The login process. The shell. The basic text editors. *Everything*.

      It was a very fair call in 1991 to say that the Linux distros of the time were just GNU plus Linux. I remember even in 1992 when people asked "what's this Linux thing" the basic reply was "it's that GNU OS but with a different kernel". It's no longer a good call because there's far more in a modern Linux distribution than GNU plus Linux but there's no denying that the UNIX-like core in any modern "Linux distribution" is mostly GNU[1].

      Yes, there is a GNU/BSD. No, it's not the same thing as the "GNU utilities" running on top of FreeBSD. It is the entire GNU reimplementation of UNIX running on top of the FreeBSD kernel. But running the "GNU utilities" on top of MacOS X or Windows would not make them GNU/Mac or GNU/Win, because GNU is not essential to those operating systems. They have their own startup and login behaviour, their own system libraries, etc.

      [1] Actually even that is becoming less and less true. Modern distros occasionally swap out GNU components for BSD components or whatever. The Free UNIX scene is rather incestuous. There is a lot of cross pollination occurring.

  22. SCO Intellectual Property License for Linux by unknown_host · · Score: 2, Funny

    well, for starters you need to buy the SCO Intellectual Property License for Linux which can be nowwww bought online at a special discount price of $49.00 only for desktop users. So hurry..while SCO^H^H the offer lasts...

  23. To really get off linux must... by Anonymous Coward · · Score: 3, Insightful

    Abandon a piece of Unix tradition. Namely the importance of commandline. Why?

    The most promising Linux newbies are those who aren't computer newbies but who are yet to be turned into Linux users/advocates. I'm talking about the people who have wide knowledge of how computer and windows work. Those that do patch, run firewalls, set up networks for their buddies and so on. Unfortunately they also like how Windows works. By GUI.

    Now, they're a good target because:
    - They decide the computing trends
    - They know enough to get Linux up and running
    - They also can be courted with things that Linux does better then Windows

    But they're also a difficult target because:
    - They aren't really interested in learning new stuff. Knowing stuff is a means to an end, not an end in itself.
    - UNIX way is way too hard for them and without commandline Linux isn't as complete as windows is.

    But as the computing trendsetters they truly are a group that must be courted in order to get Linux a wide acceptance.

    1. Re:To really get off linux must... by jedidiah · · Score: 2, Funny

      Perhaps they don't really like how WinDOS works?

      Did you ever consder that?

      Some people may actually feel more comfortable with bash or tcsh. Denying such options to them denies their indiviuality and their essential humanity.

      You would treat us all as generic grey boxes.

      That's really not the point of the market diversity that the invisible hand should be providing us.

      --
      A Pirate and a Puritan look the same on a balance sheet.
  24. Linux! It's the new priesthood, baby! by zerofoo · · Score: 3, Interesting

    Please! Love or hate microsoft, you can thank Bill Gates and company for making computers accessible to everyone. Without the sea change that was microsoft, most tech guys here would not have jobs - why you ask?

    Because there would be a lot less computers used by a lot less people.

    If Linux is going to really revolutionize the industry, then useability needs to be at the forefront of its design. As a network administrator, I want to get calls from my users when stuff legitimately doesn't work. I don't want to get calls from users asking me to help them browse their filesystem, or figure out how to center and bold a title in OpenOffice.

    -ted

  25. let homer design linux by happyfrogcow · · Score: 5, Funny

    ever see the Simpsons where Homer designs a car? that's how Linux would end up if we let the newbies do it all.

  26. The Linux Learner's Guide by ValourX · · Score: 3, Informative

    Too bad more beginners don't know about it:

    Linux Learner's Guide (PDF)

    -Jem
  27. What newbies want. by ObsessiveMathsFreak · · Score: 5, Insightful

    No more command line.

    What's That! Blasphemy!! BaSH him to Death!!!

    Seriously, I challenge someone out there to make a distro where a user need never resort to the command line interface or a terminal of any kind.

    I guess something like....Windows really...

    If you ask Aunt Tillie to type
    rpm -ivvf lovelyrpm-withnoguitoinstall-2.3-5.rpm

    she will, legitimatly I think, return to windows. She's a busy person with no time to appreciate the finer points of red hat package management.(Or why up2date keeps crashing)

    P.S.
    This does not say that you must get rid of the command line altogether mind. Even XP still has the command prompt, hidden away somewhere.

    --
    May the Maths Be with you!
  28. Other resources... by bbowers · · Score: 2, Informative

    Another great place for linux newbie help, http://www.linuxquestions.org/ complete with forums and Wiki!

    --
    Even a stopped clock gives the right time twice a day.
  29. Resolution by hartba · · Score: 4, Interesting

    That's 50% of the reason I won't use Linux on my desktop. If I install it, I get one of two scenarios. 1- The screen res is at 640x480 and looks like crap 2- The screen res is at 1600x1200 and I can't read a single piece of text. When I try to change the resolution I either get the screen scrolling around on the monitor or I get a small square in the middle of the monitor. I've used Suse, Mandrake, Knoppix and Red Hat with varying degrees of success but my main complaint is that I don't have a drop down box that will let me adjust screen res, like I can in Windows. At least it's not as functional as the one in Windows. The other thing is Samba configuration. I may be crazy but file sharing on a Windows network should've been the EASIEST thing to configure in Linux. It's the only way that Linux will ever compete in the desktop market. I've been a computer tech for years and have used everything from the TI99/4a, a 286 running a proprietary OS called "8n1" over DOS, to my latest Windows XP machine. I dictate what my family uses as their OS (because I work on their computers for free) and if I can't configure it like they want it, how are they ever going to be able to do it? After working all day long, I don't have time to weed through hundreds of man pages, only to find out there are 10 apps that do what I need it to do, but none of them will do it without editing several files and recompiling. Also there needs to be a big red button in the center of the Linux screen that says - "I really screwed up bad, please set everything back to install defaults"

    --
    60 percent of the time, my comments are right everytime.
  30. Avoid Supply Side Arrogance by 4of12 · · Score: 4, Insightful

    we will let newbies show and tell us what they need.

    This is an excellent idea.

    A lot of people in IT have a lot of experience with Microsoft, whose approach since they gained market dominance has been to more or less shove new products to their audience after some token sampling of the marketplace.

    But FOSS is currently making a similar supply-side mistake, too: people that want to use Linux to do something in particular for their business have to "just accept" a distro and what's out there. Before you say "but they can write their own app", think - How many small business owners are capable of "writing their own app", modifying an Apache module, etc?

    Sure, there's tons of free and open source software out there that people can use to build systems for their businesses, but many of those small business owners have little time or little expertise about how those pieces could be put together to help them. They need help with insight. Call it marketing, for lack of a better term.

    Instead of just offering a supply, either as MS offers OurOneSizeFitsAll - take it or leave it; Linux offers an OceanOfFreePartsAnyExpertCanUse, drive a focus more onto customer demand that will help provide more people with Linux solutions that can really help them. And, if it helps them, it will help even more people as they can more easily see how it can be done.

    --
    "Provided by the management for your protection."
  31. that's a good one by zogger · · Score: 3, Insightful

    but it's not contained within the distro when you install it, you might not even be able to get online at all to find it, and if you did, you would have to know it exists in the first place. A lot of the problems with linux and newbies or intermediate level is that it's not WITH the installation. If you are lucky enough to have a friend or LUG handy to get you started, it's probably a lot better, but sometimes that isn't possible, and a lot of people only have one computer, so if they install linux and then get stuck, they are en-screwed pretty quick if they can't go find any decent help for one reason or another.

    I agree though, task oriented and written in normal english with zero acronyms is a better idea. To ME that would make the difference between say just downloading or buying a cheap copy or paying a reasonable fee for a distro direct from the distro seller. I've gotten slightly past the total newbie experience, but initially it was a struggle, coming from an almost total no-command line background. And I'm about done registering with a buncha forums just to ask a question or take part in the conversations, I really don't want to use my email addy much anymore. I used to, but back then I got tons of spam, now that I don't register to new places or get on news lists I don't get much spam. I know that's a side issue but it's effective in keeping the box clean too.

    Back to the subject, tell you what would be *nice* is if there was a program that would mirror what you are doing in the GUI right in the console in real time, just keep following along with what is going on just as if you were totally running from the console. Say you go to open a program, the console automagically types out what the command would be, and so on as you are using the program, say sorting through the file manager, and etc. Kind of like when the GUI will give you the keyboard shortcuts when you pop open a menu item, but *better*.

    1. Re:that's a good one by stevey · · Score: 2, Interesting

      I don't know what boxed sets are like nowadays, but my first set came with a couple of simple (thin) books that explained how to do common tasks.

      Sure this raises the cost for newcomers, but having a simple guide printed out along with the ISOs is a good idea.

      I wonder if any of the places like cheapbytes will sell you a cheap ISO and cheaply printed out introduction to Linux - sounds like it'd be a match made in heaven.

      (Although maybe new-comers to Linux aren't coming from the cheapbytes route at all - hard to say I guess).

  32. You forgot... by gillbates · · Score: 4, Interesting

    Anti-virus software and monthly security updates and bug patches.

    The typical Windows user has become so adjusted to the idea of constant crashes, security holes, and bug fixes that they'll think Linux is somehow lacking if it doesn't provide them - constantly. After all, viruses are a normal part of computer operation, right?

    And should you try to convince them otherwise, they won't believe you. I've actually heard pro-Windows CS students say, "Well, it's impossible for a computer system not to crash from time to time..."

    Sometimes I think that Windows is Bill Gates' revenge against all those kids who used to make fun of him on the playground. He charges Joe "corporate-fool" Sixpack exorbitant amounts of money for the software equivalent of a Pinto - sweet revenge indeed!

    --
    The society for a thought-free internet welcomes you.
    1. Re:You forgot... by dave420 · · Score: 2, Informative

      Constant crashes? Can you PLEASE put that old-ass dig to bed. XP doesn't crash. I've not had a crash on my PCs for months and months and months. I mean seriously - it harms the linux community when people, supposedly IT-savvy, keep banging on about crashing when it just isn't true any more.

    2. Re:You forgot... by gillbates · · Score: 2, Interesting

      Ah, yes, but the idea of Windows crashing has not left them....

      Oh, and how's your system restore work?

      Thought so. Mine didn't work either. I've used XP, and it is junk. Try inserting an unreadable CDROM in the drive sometime, and watch XP become useless for about 5 to 10 minutes, if it recovers at all.

      That bug has existed since Windows 95.

      Granted, the days of Windows suddenly refusing to boot are probably past us, but the OS as a whole is still trash. To a Windows user, the aforementioned bug is crashing. Most people won't sit and wait for 10 minutes - they'll reboot the machine, "because it crashed on me."

      And when this happens, they're reminded of all of the past problems they've had with Windows. In spite of any actual progress Microsoft might have made, it's these highly visible flaws which only reinforce the notion that Windows Crashes(tm). Users can never be too sure of their system's reliability because of the number of times in the past that crashes have happened without warning.

      It's not so much the actual state of the software, but the fact the Microsoft has just released so many buggy versions of Windows that users can never be sure if the software will work or not. Granted, XP might not crash on your system, but too many people have burned too much midnight oil to restore crashed Windows boxes to go back to using Windows on the advice of just one person.

      --
      The society for a thought-free internet welcomes you.
  33. Blaming Users For Defective Software, Eh? by reallocate · · Score: 2, Insightful

    >> Users need to be educated, there is no alternative.

    Nuts. This is just another way to blame users for software that isn't good enough.

    Better to write software that doesn't require an education than whine about users.

    --
    -- Slashdot: When Public Access TV Says "No"
  34. set up a FIREWALL??? by silicon+not+in+the+v · · Score: 2, Insightful
    I remember seeing that before when they were contemplating a few things people should try for this project. I can't believe they didn't wise up and leave that out. This quote from the article seems to say it all about that idea.
    You may not want them to try to set up a firewall on your machine, for example, if you already have one set up and it's too awful to contemplate having to wipe it out and start fresh.
    Oh yeah, that sounds great that you should try to have a newbie set up a firewall, even though it's a royal pain in the ass for the knowledgeable Linux user. WTF?!
    --
    We may experience some slight turbulence and then...explode. -Capt. Mal Reynolds
  35. Knoppix can be as usable as Windows by WarmBoota · · Score: 5, Informative

    Recently, when my hard drive borked, I had to resort to using Knoppix to check my email, et cetera while waiting for the spare time to get things working again.

    With a Knoppix CD, I could:

    • instantly boot into Linux (look Ma, no install!)
    • Access my USB Memory stick
    • Create a word processing document
    • Print to an HP Inkjet (the configuration was actually less painful than the Windows procedure which dumped hundreds of megs of junk on my hard drive)
    • Access web-based email with Mozilla

    Now this was incredibly usable to me since I am familiar with Linux in the first place. There are only a few places where things fall apart.

    1. Knoppix can be installed to the hard drive, but typing "knoppix-install-hd" at a root prompt isn't the most discoverable interface.
    2. I know that k3b burns CDs and Mozilla is used for the Web. Until Linux applications have brand-name recognition of things like QuarkExpress or Excel, I think that application names need to be more descriptive, or some other mechanism is required for users to discover the application purpose. KDE is pretty good with sorting applications into Internet and Graphics folders, but it could be done better. I wouldn't find a hand-holding introduction useful, but others might.
    3. I was able to use konqueror to browse a Windows network, but again, this is only because I knew that I could type smb://ipadress/share.

    I think that the Harmony Remote concept would be useful for Linux Configuration. For those too lazy to Google for it, the concept is this:

    1. Answer some questions on the devices that you actually have (e.g. Do you have a TV, Stereo Recevier, DVD Player, etc).
    2. Identify the model numbers (I know that this is a stretch for basic users, but bear with me).
    3. Answer some questions about how you want things to work. (e.g. Do you control the DVD volume with the TV or with the Receiver).
    4. Once that's complete, activities appropriate for each device are created. The Linux equivalent would be a walktrhough tailored to their machine (Printing, Scanning, Internet, Local Network, etc).
    --
    90% of everything is crap. Also, crap is relative.
  36. How about letting newbies know what's available by JBMcB · · Score: 3, Insightful

    First step is letting neophytes know what is out there. There are loads of different distributions, applications and desktops, and it's difficult for new users to figure out what they want.

    What would be helpful is a site like Freshmeat, but set up for new users, ideally like a software store. You could look for apps under various headings, and install them by clicking a link. Maybe a Mozilla plugin that autodetects what OS you're running on and grabs the appropriate rpm/deb/ebuild/whatever. Ximian has something like this, as does Lindows, I think. But it needs to be even easier to use than their systems.

    While we're wishing, how about a consistant interface for help? Base it on XML (Docbook?) and make it possible to import info and man pages, and make it auto-update from the net with bugfixes, changes, and news. I really like the old Microsoft help format, about Win98 vintage, not HTML help yet but it could display HTML and had a nice contents page and tree-style index. Hmm, time to start coding...

    --
    My Other Computer Is A Data General Nova III.
  37. blind leading the blind by CAIMLAS · · Score: 2, Interesting

    Do we let undergraduates tell the professors what they need to know? Do we let middle schoolers decide on their curriculum? No?

    The point being is this: newbies do not know what they need, anymore than the examples above, or the person buying a Dell running WinXP which comes with only 128Mb of RAM.

    I'm tired of people trying to make linux something that it is fundamentally not. Linux is not designed to be an OS for the masses; it is designed to work. Breaking that paradigm will inevitably break the core of what Linux is.

    --
    ~/ssh slashdot.org ssh: connect to host slashdot.org port 22: too many beers
  38. Doom to fail... by Atomic+Frog · · Score: 3, Insightful

    Because they still don't _get it_!
    GrokDoc is asking about the _applications_, and that's not the problem. Mozilla on Linux is the same as Mozilla on Windows. OpenOffice is the same on both platforms.

    It's the system, stupid!

    If I install an application on Windows (or Mac or OS/2), where does it show up? Usually on a nice folder on the desktop or on some sort of "system menu". In Linux? Usually the answer is "I don't know!". (Problem is, some will play nice, some don't). Even if I knew to get to the command line, where is it? It's usually not fixed my $PATH variable, so it doesn't point to it yet. So how do I find it?

    In any other OS, it's obvious. Look in "Programs" or "Program Files". Bloody obvious. Linux? Err...is that /usr/local/bin? Or maybe /usr/bin? or /usr/local/apps? (I've seen it in all 3 and more), not to mention NONE OF THESE PATHS MAKE SENSE TO YOUR AVERAGE USER!!! Even if you explain it to them.

    And last of all, don't tell the user to RTFM. Most of these FM's are derived from man pages, which are F*** all useless to your average user.

  39. RTFM??? by lewindha · · Score: 3, Insightful

    Here's a big problem with Linux. Linux users want people to switch to Linux, but they're not willing to help. It's always, "Did you 'man' it?" or "RTFM!!!".

    People are used to turning the computer on and using it. I dual boot with XP Home and Fedora 2, I do not consider myself a Linux guru, but I know how to get around.

    For the most part, Windows is easy. Linux is not if you grew up using Windows that last umpteen years.

    Some of you will hate me for this, but the billions of distros doesn't help. With Windows, there's only one. Having a computer background, I can say I enjoy having a choice in my flavor of Linux and desktop. But the everyday user will look at this as a hinderance. They don't want to choose the wrong one. Not everyone is a Unix admin or a developer.

    You can't find the same program in the same place on different distros. Or if it is, it's not given the same name. In Suse, XMMS is 'XMMS', in Fedora Core 2 it's 'audio player' or something like that. Not a big deal to the normal Linux user, but a huge deal to the everyday computer user that grew up on Windows. When they install Winamp, they're gonna find it under Winamp, not Audio player or anything else.

    Not to mention the amount of upgrades different distro companies produce. People don't want to feel like they have to upgrade every six months to a year.

    You can flame me all you want. The truth is, I love Linux and enjoy the upgrades, etc. But the normal computer user is discouraged by all of this.

    Until Linux works with all hardware(it won't work with my Lexmark all-in-one) and is unified in it's overall look, normal users won't adopt it.

    --
    Eric Windham
  40. manuals and learning by zogger · · Score: 2, Interesting

    my first distro was just someone I knew made a copy and gave it to me. that was enough to get me installed, but not online with, but luckily I have multiple computers so I was able to go find out what I was missing and doing wrong. Second distro was a boxed redhat 7.2, that came with two good paperbacks that had *some* useful info, but if what they said didn't work when you tried it, then back to googling here and there and yonder. Since then I just buy shipped-cloned because I am on dialup, well, don't own a burner either, running FC2 now, but that's only because I can go look up whatever I am stumped with, but I also have a lot of patience and the backup computer that I know very well, my trusty old mac classic, can get me to the web to find info. If all I had was the one computer, no way would I still be running linux, and driving an hour round trip to go to the library is not an option. I guess you just really have to WANT to run linux is what I am saying, to make it worth your while. I never went through windows insecurity, so that wasn't a factor in getting me to switch, I switched because steve jobs priced me outta macs to be frank, not because I didn't like them or couldn't figure things out, on the contrary, I always found classic to be fairly easy to use with zero instructions beyond click here, it does it. I never understood using windows *on purpose* as in going out and actually paying for it, and I never even saw anything unixy before I tried linux.

    Yes, printed out instructions that could be included with a clone copy for another buck or two would be a pretty nice addition. I find any of the built in information I have seen to not be of much use unfortunately, for one, it's hard to keep track of what you are doing when all of it is brand new, better to have a dead trees manual by your side while you try to make sense of what is on the screen in front of you, at least it keeps the clutter down and you can scribble some notes in your manual as you tweak stuff.

    I still like my idea of a command/GUI real time mirror though. Or even take it further, to build up the mind/muscle-memory deal, you start the mirror program, it forces YOU to follow the example that is indicated and to type the command, almost like a typing tutor but to learn linux, while you are actually doing what you want to be doing, not what they want you to do.

    Hmm a name for the GUI/console mirror tool... heh heh heh , perfect for /., although someone's mom might not like it....

    Command Line Interactive Training

  41. Finally, somebody with a clue about usability by Animats · · Score: 2, Insightful
    • Have them try to do a minimum of four things: email, a letter (including printing it), a firewall, and surfing the web. (That includes setting up for email and surfing the web.) Ask them to log out at the end. What do they spontaneously say they like and what do they say upsets them? Is the menu clear? Where do they get lost? Record what you see, not just what they say. If they have a prompt on the screen, and stop for five minutes trying to figure out what it means or how to move past it, note such bumps in the road, even if they eventually solve it.

      Watch them try and record the results. If you have a video, and they are willing, record it for your own use so as to analyze carefully what happens.

    That's how usability testing is done. Although, to do it right, the user should be alone; no hints. And you need video and audio of the screen and the user.

    It is worthwhile to make a highlights reel from such videos for developers to watch.

  42. Re:LinuxQuestions wiki ! by MikeCapone · · Score: 2, Informative

    I take back what I said, I hadn't noticed at first by Grokdoc and LQ.w have different aims and, anyway, both websites have the same webmaster.

  43. Experts don't always RTFM either. by Chemisor · · Score: 2, Interesting

    I don't know about you, but if I have problems installing something, I don't always RTFM either. For example: I tried many many times to get wine to work, and every time failed. It crashes, or can't find some config file, or just doesn't do anything at all. Why didn't I RTFM? Because it is BIG and I just don't want to waste all that time to figure out just what options I need to type into the darn config file. Instead, I just boot into Windows to play games. Much simpler, not wasted time, no strange crashes, and everything is supported, including my nVidia card. Another example: printing. My machine can not print right now because the printer is networked from a Windows machine and magicfilter crashes for some reason when used in the smbprint script. Could I debug it? Probably, but why waste time? If I need to print a letter, I can just boot into Windows and use Word to type it and print it. Much simpler than spending hours messing with unfamiliar code in gdb (don't you just _hate_ gdb? It's another example, by the way. It is simpler to just put some printfs into the code and recompile than to figure out why it suddenly loses all my symbols ["can't find class string as reported by C++ RTTI"]). So, as you can see, unless the failing program does something vital to me, it is much simpler to just boot into Windows for a while, do it, and then reboot again and go on living.

  44. Programmers are poor writers. by Spencerian · · Score: 5, Insightful

    I'm a computer tech and consultant that generally putters with programming. I wasn't too shocked to see, as I moved to Mac OS X, how badly the man help and documentation files were written.

    My career involves many publishing venues, including a very popular book publisher and a city newspaper. While most developers are very adept at their work, self-expression or documentation is not their strong suit in general. The text is jargon-rich and circular, presuming that the reader already has a knowledge base equal to that of the writer.

    This one point alone is why Linux and almost all other UNIX blends and clones never get the attention they seek. It's not that the OS is rotten (far from it), but because users have NO FRICKIN' CLUE what to do with it, including installing the OS (which programmers should really assume will be atop or supplementing Windows), and the help information is incomprehensible, if it exists at all.

    Further, the diversity of X Window-based interfaces (window managers and desktop managers like KDE) are too diverse, leaving users very confused where anything is. Mac OS X is essentially the only UNIX clone/blend that a grandma can use. Sure, grandma CAN use Linux, but who's going to teach her how in a way that is understandable? She certainly won't try to READ how.

    My humble opinion is that programmers should stop trying to steal the likenesses of Microsoft Windows and Mac OS X and attempt to kidnap the companies' marketing and human interface staff!

    --
    Vos teneo officium eram periculosus ut vos recipero is.
    1. Re:Programmers are poor writers. by cluckshot · · Score: 5, Insightful

      I will second the motion on MAN pages being stinking rotten messes. I have tried for years to read them and tried to make any useful sense of them. The problem is that they give you a command name and a set of switches and input values not considering that many combinations have no real value or simply don't work together.

      I could use a man page with a few examples for how to use the command. Try chmod for example. Goof around with chmod in a recursive fashion and you are likely to have the OS fail to work! It is easy to not know that unless a program is not editable it will fail to work.

      Take the wonderful commands for applications of grep!!! Which goes with which and which conflicts with which and why.

      Well if you are not confused you have not tried these wonderful tools. They are powerful but obscure. A MAN page which actually gave you a useful script like command [Switches] [FileName] and actually showed you a simple examle or two might help. tar for example can be pretty awful without a good example.

      I suppose a wrapper tool might be in order as well

      --
      Never Politically Correct ~ I prefer the facts If you don't like what I say, get a life, or comment yourself.
    2. Re:Programmers are poor writers. by bangalla · · Score: 2, Informative

      The best help system I have ever used is in VMS. You simply type 'help' at the command prompt (how novel) and you are presented with a list of options. You continue to drill down through the list until you get the information you want, examples, subcommands, everything you could want.

      It's worth trying to find a VMS box to log on to just so you can see how documentation should be done, it makes man pages look like the confusing mess that they are.

      --
      I want to use these Mod points but I can't find anything Interesting, Informative or Insightful on Slashdot.
  45. I call shenanigans! by leoxx · · Score: 2, Insightful
    Unless you can somehow prove that without Microsoft there would have been no computer industry, then your argument holds no water. In fact it is worse than that; unless you can prove that without Microsoft there wouldn't actually have been a BIGGER industry, employing MORE people and serving MORE end users, you argument falls completely on its face. One need only look at the pricing history of Windows to see that the OS, which originally was a small portion of the cost of entry for end users, has now become a major part of the cost of entry to many users, especially in the third world. And lest we forget, "incompetent competitors" are not the only ones to blame for this state of affairs.


    But anyway, back to the topic at hand. I think we both agree that at the moment, usability for most people is equated to having a Windows look and feel. The real challenge to the Linux community will be to get to a point where Linux's usability can be judged independently of whether or not it looks or works like Windows. This is something Apple has been quite successful at.

  46. Newbies WANT to learn Linux! by ggvaidya · · Score: 2, Insightful

    Don't confuse the issue!

    This webpage isn't intended for computer newbies - people new to computers altogther. This is for people who want to make the Windows (or MacOS)-to-Linux transition, and need help doing it. There's still an awful lot DOS/Windows people need to learn to progress to Linux, and I think it's knowledge worth having.

    All I'll say is: more power to them!

  47. Re:Linux! It's the new priesthood, baby! by grouch · · Score: 2, Informative

    "Please! Love or hate microsoft, you can thank Bill Gates and company for making computers accessible to everyone. Without the sea change that was microsoft, most tech guys here would not have jobs - why you ask? Because there would be a lot less computers used by a lot less people."

    Nice re-write of history to match your fantasy. Bill Gates and company didn't make computers accessible to everyone. Bill Gates and company opportunistically snatched a dirty clone of Gary Kildall's operating system after selling IBM something Bill Gates and company didn't have.

    There was no "sea change that was microsoft" except for the change from collaborative computing to antagonistic computing, from a model following the scientific method of progress to a model of greed. Bill Gates and company have been holding computing back for twenty years. Evidence in the real world? Linux.

    By the time Linux was 7 years old, it was already the number one threat to MS. (I'm sure you can search Google for those terms. Hint: Ballmer is the one who proclaimed the threat). MS had how many years by 1998? Yet the "upstart", using collaboration instead of secrecy, with enlightened self-interest to motivate instead of greed, and using a license that protects the USER instead of enslaving the user as a revenue generation unit, overtook Microsoft. They've been falling behind the penguin ever since.

    I note while reading the comments that much of the whining against Linux and much of the promotion of MS comes right out of the CDs, handbooks and publications MS put out beginning in 1998 about how to deal with Linux. It's time to read Bill's memos at opensource.org/halloween and give up on the FUD. It doesn't work.

    Business is waking up to the fact that it needs Linux. They are stampeding away from the ever-tightening cage that MS is attempting to lock around them. Microsoft's desperate rush to patent, while the USPTO is still rubber-stamping everything, will not be sufficient to stop the stampede.

    Individuals have discovered that there are distributors of Linux who work very hard to make things easy. People are fed up with the continuous, expensive, damaging, time-consuming reminders of the low quality of MS products, which reminders come in the form of service packs that break existing "applications", viruses that eat data, exploits that allow MS "extensions" to standard HTML to hijack and control their computers. People are fed up with MS telling them they must not do this or that, with the threat of U.S. Marshals and the BSA kicking down doors. People are fed up with the increasing invasion of their privacy in return for the privilege of paying ever higher subscription fees for software that provides more functions for exploiters than those who pay the rental.

    Linux works. Linux is easy enough for kindergartners to use, now. Linux has already revolutionized the industry. Linux sets individuals, businesses, governments and schools free from the illegally obtained, maintained and extended monopoly's choke-holds and its unwanted and unwarranted intrusions. Linux lets you own your computer, instead of being 0wn3d.

  48. No by ciaran_o_riordan · · Score: 2, Insightful

    people don't use an "X/Linux" system, they use a "X/GLibc" system. Linux can be swapped out in favour of the FreeBSD kernel if you like. Your user space apps call GNU Libc, not Linux.

    In 1983, X and TeX existed, RMS decided we needed a free OS. So he started writing one. He personnally wrote GCC, Emacs, and GDB. He recruited volunteers, he founded FSF (who hired 15 programmers), he wrote the GNU GPL, he asked people to help again and again and he gave them the tools to write free software. He gave talks, he spoke to the media, he answered slashdots questions, he has worked and worked, and produced more than anyone else has for this OS.

    Linus Torvalds found the tools made by RMS and wrote some free software (it was proprietary initially but Linus GPL'd it in 1992). Linus (accidently) finished the GNU project, the pure GNU OS didn't have to be finished because a variant using Linux as it's kernel was ready.

    You can call it "GNU/Linux" out of respect for the GNU programmers that wrote the largest chunk of the OS, or you can call it "GNU/Linux" because that's the only name that keeps the topic of freedom in the conversation. (IBM and MS have neither of these goals, so they call it "Linux", please don't just copy the Megacorps.)

  49. What newbies need... by RyoShin · · Score: 2, Insightful

    ..Are for true Linux users to stop telling us to RTFM.

    I have a Linux zealot living at my fraternity house with me (we're mostly a geek fraternity,) and he will go on and on about how great *nix is. Since I went to a public school with the bare minimum in extra-curricular, I've grown up with Windows my entire life. I'm 19, and the most experience I've gotten with any kind of *nix is the command prompt on a solaris box and some basic SSH (which I'm not sure even counts.)

    We have a router at the house running OpenBSD (that this Linux zealot designed,) and the current section (I go to Kettering U, if anyone knows what that means) has messed it up a bit. I was trying to fix it on my own, and I was thinking that I could e-mail this guy (who lives an hour away or so right now) to help me on it. He gives me the SSH info, and then keeps saying, you guessed it:

    RTFM!

    Which would be great. Except, being a linux n00b, I don't have a damn clue what M to F R! If I knew the commands I needed, but didn't know how to use them, RTFM would be expected. But I don't even know the commands to start out with (yes, I know about man man, but that doesn't help me a lot with editing the file that controls the router, or even where to find it.)

    I guess the basic answer would be: Support from those without egos the size of Texas, and little to no conceit. That would be nice...

    Reminds me of a Bash quote that states that, to get a real answer, you have to troll Linux forums/newsgroups. I haven't tried that, but I expect I may have to.

  50. about time by bob+dobalina · · Score: 2, Interesting

    I am a software engineer who's been using Solaris for about 8 years now and just recently switched to linux as a result of a job change. Much of the switch was painless enough, but there are a few differences between the two that needed sorting out, as well as using new software and doing sysadmin things that I previously had smart people paid to do for me.

    My local linux guru happens to be a good friend of mine, and even when I come to him with seemingly intelligent questions, I get borderline hostile responses, suggesting to me I am an idiot/asshole/whatever for daring to waste his time with a question that I could've found the answer to myself.

    Unfortunately, for someone of my intelligence and experience, "finding the answer for myself" usually means hours spent poring through manuals and FAQs and HOWTOs for the weird little behavioral quirk I'm looking to get answered. I dare not look into newsgroups and ask, for fear of even harsher treatment.

    Most of the time, the people complaining about how idiotic newbies are, are often the same people wondering why linux hasn't taken over the world, established peace and harmony and cured cancer. Quite simply, it's not because people aren't curious about a free operating system and tons of free apps to do what people normally pay to do -- it doesn't take a sociologist or economist to realize that people will gladly do the same things they pay for, for free, given the chance. The problem is, they need to ask questions, and the best people to ask generally have enormous egos and a massive elitist streak.

    RTFM/RTFFAQ is not without it's merits, but unfortunately many linux geeks use it as a simple, smarmy response to questions one can't reasonably be expected to know or discover for oneself. RTFM is meant to stop people from wasting time with common questions, but instead it's being used to stop otherwise interested people from pursuing linux further because those already steeped in it treat them like idiots. People like free software, but they don't like being insulted to get it.

    One of the reasons Microsoft ascended to where it is now is not because they make high quality, stable, efficient, easy to use software. It's because they treat their customers like gold, help them with their problems happily, and treat even the most idiotic questions with empathy. Linux users looking to evangelize the movement should do likewise. Remember, you were there once too, not knowing how the hell to install patches or configure a Samba server or get your network running. Just because you have the knowledge doesn't make you a better person, unless you REALLY embrace the open source movement and make your knowledge as open source as the software.

    --

    B

    "I'm payin' taxes, but what am I buyin'?" -- James Brown