Slashdot Mirror


The Clueless Newbie's Linux Odyssey

overshoot writes "Just what we've always (said we) wanted: people who are fed up with Microsoft and are willing, even eager, to give Linux a real try. Well, she did. And did. And did some more. Not only that, she's a technical writer and she took notes. Not fun reading, but worth reading anyway."

16 of 644 comments (clear)

  1. The Real Problem... by JJahn · · Score: 5, Insightful
    is that most people don't understand that Windows is not the universal basis of good operating systems. People expect everything to work the same as it did on Windows. Of course that has to be the case for wide-spread desktop acceptance, but IMO that is not the way it should be.

    At least Linux is reliable and after you get used to working with it, is powerful and useful. And also I don't seem to have so many damn device driver problems as in Windows...with those clueless vendors writing garbage drivers (I'm thinking Creative and ATI at the moment, grumble)

  2. nice quote by mrpuffypants · · Score: 5, Funny

    Well, you shrieking geeks

    that's a nice way to endear yourself to the readers. I'd like to read some of her technical writings...

    Now configure sendmail; you know where the sendmail.cf file is, you twit!

  3. Not a lot of variety by 1nsane0ne · · Score: 5, Insightful

    Let's see 12 distro's tested. Of those 8 are red hat / mandrake and 2 were suse. To give linux / alternative operating systems a try there should be more choices. She never said that linux was her only choice she just thought it best met her requirements. Seems to be that FreeBSD or any other BSD would be a good choice to try at as they meet all the requirements. Or if your hell bent on linux at least use a bunch of different distros just not red hat and mandrake. Doesn't seem like she gave enough alternitaves a try. I'm personally a fan of using what works best, be it windows, unix, linux, bsd, mac, beos, or whatever. It varies from person to person and from situation to situation and from computer to computer. There is no end all perfect for all, hardware, situations, and uses operating system and until there is one, we'll be stuck dual booting or using windows in some situations or whatever. Anyways thats just my two pennies.

    1. Re:Not a lot of variety by overshoot · · Score: 5, Funny
      Let's see 12 distro's tested. Of those 8 are red hat / mandrake and 2 were suse. To give linux / alternative operating systems a try there should be more choices. She never said that linux was her only choice she just thought it best met her requirements. Seems to be that FreeBSD or any other BSD would be a good choice to try at as they meet all the requirements.

      Help me here -- she's having trouble with Mandrake's installer and you want her to try the BSDs?

      --
      Lacking <sarcasm> tags, /. substitutes moderation as "Troll."
  4. what about from the other direction? by timothy · · Score: 5, Interesting

    First: This article makes some very good points, ones that people who push Free and otherwise Open Source software on others to the point of being annoying (like me) often have to skirt around. This kind of criticism is really important!

    Second: The author talks about the need (in her case) of a dual-boot system, and that's surely a common situation. However: What about Windows? If someone has a mostly happy, generally successfull Linux installation on a machine with a few tens of gigs of hard drive space, can Windows be nicely (non-destructively) installed as a novelty or ... for what Windows users use it for?

    I have installed Mandrake Linux (versions 7.1 and 8.0) on Laptops which arrived with different versions of Windows, and contrary to the upshot of this article, those installs (dual-booting with Windows) went pretty automagically (though I regret that I ended up with a big never-used partition on each of those hard-drives ;)). However, that's because Linux distros know they exist in a MS-dominant environment. Microsoft seems to offer tips on removing Linux, but how difficult would it be to go about creating a dual-boot system the other way?

    (This question is out of ignorance, and is not rhetorical.)

    timothy

    p.s. A very similar, just-as-damning article could be written about the various interface flaws that infest Microsoft Windows; a few recent visits to my dad, trying to help him set up wireless networking under Windows led me to show him how if I popped in a Knoppix CD, everything Just Worked, but we never did get Windows XP happy with his network.

    --
    jrnl: http://tinyurl.com/c2l8yr / foes: http://tinyurl.com/ckjno5
  5. Before everybody piles on... by Fritz+Benwalla · · Score: 5, Insightful

    I have to add that this was my experience too.

    Let me preface this by saying that I run a web design company, I maintained our servers for the first few years, I put in my time on PETs and TRS-80s, and APPLE IIs and Windows 3.0 and 95 and NT and 2000 and Linux. Take my word for it, I'm a seriously fucking technical guy. I offer as further evidence the fact that I'm posting to Slashdot on the Linux holy war at 9pm on a Saturday night.

    I made an honest go of making my home main OS Linux, but I quit in frustration. The main problem is that it's not that Linux isn't *capable* of doing everything I need, but the tiny things that are slightly greater hassles in Linux end up being a death by a thousand cuts.

    If there's one main way I can think of to characterize my regular use of my main OS, it's "freewheeling." I need it to be a transparent conduit in my productivity, whether it be hitting the Net, writing documents, personal finance, etc. Linux was *always* functional, but *never* transparent. I constantly had to tweak little things to make it work, find new libraries, etc. That's fun when I'm using hobby time, but not fun at all when I have shit to do on a deadline.

    Honestly, I don't know how you're going to fix this aspect of the OS without doing what Microsoft has done - compromise fundamental stability and security in favor of useability. Personally I hope the debate stops, and we stop trying to fit a square peg in a round hole. Let MS spend their money catering to the masses, let's keep Linux stable and robust for hard core needs.

    I think we'd be doing the world a lot more good putting Microsoft's server products out of business than their desktop products. I'd feel a much greater sense of accomplishment knowing that I helped get the world's credit cards onto a Linux server than the world's Mom's on a Linux desktop.

    -----

    --

    Believe me, I'm as surprised by my comment as you are.
  6. Re:Brief comment by richi · · Score: 5, Informative

    The different direction of slashes is due to MS-DOS using '/' as a way to denote command-line options (e.g. DEL /S/F *.* ). Early version of DOS didn't have a heirachic filesystem, so when MSFT added the concept of directories, they couldn't easily choose '/' as the separator, so they thought that they should use '\' instead.

    Muscle memory sanity for people switching between DOS and Unix wasn't exactly seen as an issue to those guys ;-)

    r.

  7. Re:Article Summary by Pyromage · · Score: 5, Insightful

    Your attitude is why Linux sucks so much.

    I use it every day. I don't have Windows installed on any of my systems. I *still* think it sucks.

    Why do so many people think that it's always the users problem? Bah, it's so stupid I won't even argue this one.

    The thing is, why hasn't anyone tried to make a *good* distribution yet? We have Debian "we have ten thousand pounds of shitty, buggy, out of date software, but hell, that's a lot, so its good". There's slackware (my favorite) which just has this "you had better know how to do everything because I aint helping you" attitude. Mandrake is as broken as the above. RH is as broken as the above.

    Most niches have decent software in them. There are some genuinely good word processors for Linux. Ditto for web browsers, email clients, etc. Why package 45 shitty ones in a distro?

    And on the topic of hardware support, I'll just paint an analogy: BeOS. BeOS supported almost no hardware. It has worse support than any other OS I've used, in terms of quantity. But what it *does* support, it supports perfectly. Swap video cards? You won't get any messages. The new one will just work, same resolution, same bit depth (assuming they both were supported, but that's not avoidable). THIS is what support should be: when it works, it should *work*.

    When I installed my HP722C a while back, I had to manually write a magicfilter print filter because no existing system supported it at the time. Unacceptable.

    And people like you come along and make jackass comments like "You're not l33t enough to move to Linux, because you're still running Windows 95! Only Win2Kers are cool enough to join my OS!". Asshole. Shut the fuck up.

  8. Linux printing is a nightmare. by SlashChick · · Score: 5, Informative

    My experiences mirror this author's.

    Having administered Linux web servers for several years, I decided to set up a dedicated Linux print server at home. My printer is an HP Color Laserjet 4500 which installs easily with pretty much any Windows version; I decided to forego buying the JetDirect ethernet card for the printer and use Linux as a print server instead.

    I asked my friends what to use on my AMD K6-2 300 that had been commandeered for the purpose of running Linux (no dual-boot attempts here.) They said "Debian." I shouldn't have listened.

    dselect is the most nightmarish application I have ever seen. I spent a good 15 minutes reading the help files, most of which were of no use to me. I then somehow managed to exit out of dselect by hitting some keystroke. BAM! I was dropped into a console prompt with absolutely no packages installed.

    Aha! I thought. Apt-get to my rescue! After all, that was the saving grace of Debian. I tried "apt-get install kde." Not the right package name. Okay.... "apt-get install gnome." No? I just need to apt-get some sort of GUI!

    With tedious Google searching, I finally figured out the sequence of commands to install KDE, and I was off and running. (I think I ended up installing some calculator program that required the KDE libraries, and it went ahead and installed KDE for me.)

    I rebooted and was dropped into KDE.... exxcept that Debian wouldn't detect my USB mouse. I ended up having to go into #debian on freenode and get the instructions on how to edit some mouse configuration file just to make Debian understand that my mouse was on a USB port. After my mouse worked, I started using Debian, except that I got this weird C error dialog whenever I ran any application. I gave up and tried Red Hat 7.3 (then the latest) instead.

    Red Hat was much easier for me to use. It detected my mouse during the install program, which was nice. However, it didn't detect my printer. I finally got the printer installed under the "control panel" sort of thing that KDE had, only to find out that most of the computer's applications didn't recognize that I was using CUPS! I went back to IRC and asked what the deal was. "Oh, that's normal," was the response. "If you set up the printer under KDE, only KDE applications will recognize it! Then you have to go in and tell all your other applications that the printer is now defined under CUPS instead of LPR. A window manager doesn't control your entire system! You should learn the difference between a window manager and the underlying OS."

    By this time, I was miffed. If I set up a printer in Windows or Mac OS under the Control Panel, all the applications realize that that printer is now my default printer. Why in the world couldn't Mozilla (to use one example) do this? As far as I was concerned, the GUI control panel was the system control panel. To force users to learn the difference between window managers and the underlying OS and to force users to understand that changes they make in the window manager won't apply to the entire OS is a usability gaffe of such proportions that it hasn't been committed since Windows 95 took DOS out of the picture 8 years ago.

    It took me several more hours to set up Samba to share my printer out to my Windows XP box, most notably because of a bug in Samba that prevented sharing printers to Windows XP. I then had the printer working with over 7 hours of work. It was a very long day for me.

    I used the print server successfully for a few weeks. I then went away for Christmas and turned the computer off. When I came home and turned it on, there was no print server (and yes, I'd made sure that all the correct services were set to run on startup, which was yet another annoyance I had to consider in the 7-hour setup process.) Instead of being frustrated, I remembered that I had an old Pentium 75 in the garage that ran Windows 95. 15 minutes later, I had downloaded the Windows 95 drivers from HP's website, clicked the "enable printer sharing" button,

  9. Re:Article Summary by agentkhaki · · Score: 5, Insightful

    [sarcasm]

    Why package 45 shitty [insert software type here] ones in a distro? Choice, my man, choice.

    [/sarcasm]

    Seriously, the parent is 100% on the money. Linux wasn't, isn't, and probably never will be ready for the masses, because the masses want things to just work. Now, before everyone jumps on their anti-microsoft steed screaming 'Microsoft's stuff never does what I want it to do,' remember the following:

    1) As crappy as it might be, Microsoft offers real, live human support for their products, assuming you purchase them and don't pirate.

    2) If something doesn't work, one doesn't have to play 'find the config file and learn how to use whatever sort of configuration options the author decided to implement.' One simply a) doesn't use the product and returns it or b) finds someone to get it to work for them, which is much more likely if they're running Windows or MacOS than if they're running linux.

    3) Why *are* there so many different ways of doing things in Linux? How about one or two *good* ways, instead of half a dozen not-so-good ones?

    Joe user wants things to work. He wants to go to Best Buy, grab the latest game, gadget, whatnot, and he wants to go home, plug it in, idely stand by while it installs God-knows-what spy-ware, and then he wants to use the product, even if he has to jump through a few hoops to do so.

    And probably the biggest reason why Linux will never make it to the main stream population: UI design. Sure, Apple's got a better one than Microsoft... Or is it the other way around? The truth is, it doesn't matter - they have the money and resources to hire someone who knows a thing or two about UI design, and they have the same money and resources to conduct focus groups and research and all those things that open source simply can't do, and they can figure out what works the best for the most number of people, and not just the geeks and their playmates who happen to have written the software.

    --
    Ack!
  10. I'd have to agree by Trepidity · · Score: 5, Insightful

    I use Linux (Debian) nearly exclusively, but I can definitely see where she's coming from. If I want to do pretty much anything I need to read a bunch of documentation and edit config files. Now this isn't too difficult if you know what you're doing and have spare time, but I can see how most people would find it unacceptable. In Windows and Mac OS, if you want to do something like, say, burn a CD, you just install the necessary software and it Just Works. In Linux you have to find a cd burning HOWTO and figure out how to change permissions so the cd drive is writable by your user (or set the suid bit on your cdwriting software).

    My biggest pet peeve though? There don't appear to be any good GUI ftp clients for Linux. There's gftp, which is lacking lots of features and is crashy, and there's something-or-other from the KDE people that's not so good either. Nothing approaching Windows' BulletProof FTP or SmartFTP. So I use ncftp, which is a CLI interface. Works for me, but I doubt it would for most casual computer users.

  11. Re:Article Summary by neuroticia · · Score: 5, Insightful

    Linux doesn't suck any more than any other OS that's out there. They all have problems--name it, and it has a problem. People tend to choose their OS based on which set of problems interferes the least with the work they are hoping to accomplish on their computer. (Or they choose it based on what the shiny-piece of plastic they bought at the local CompUSA has installed... But we're not talking about them now, are we?)

    Win2k->Linux *IS* a much easier migration than Win95->Linux, because Win2k has more tools available, has a user paradigm closer to that of Linux (ie: actual security, user profiles that are not just "profiles", etc.) We're not saying that only Win2kers are "cool enough"--hell, I've seen a few WinME'ers migrate over to Linux more easily than Win2k'ers, we're just saying it's an *easier migration* because there's less to learn. (Assuming the migrating party bothered to learn Win2k in the first place)

    There are REASONS why Linux advocates say what they say--often reasons that extend past the snottiness you sweepingly accuse them of.

    As for your complaints about the distros--it's all a matter of personal preference. If you don't like it, you're not required to use it, you know? You do sound like you'd be far more happy on Windows, OS X, or even BeOS. Or are they more sucky, resulting in you staying on the Linux-side?

    Yeah, the Linux community does tend to be a bit short tempered. They're more than happy to help you work out issues, but if you keep complaining about the OS they're also more than happy to tell you to go back to whatever OS you feel most comfortable with. There's plenty of newbies that aren't whining, are more likely to listen, and less likely to waste our time by complaining about how Linux can't do X, Y, and Z--completely forgetting that their "favored" operating system can't do X, Y, or Z reliably, either.

    Anyone who's a negative little fucker is going to have a very negative experience with ANY community they venture into, and ANY OS they attempt to use.

    -Sara

  12. Linux sucks less (sometimes) by David+Jao · · Score: 5, Insightful
    If Linux "sucks so much" then why do you still "use it every day"?

    This question is rhetorical. You probably use it every day for the same reason I use it every day--that being, although it sucks, everything else sucks more.

    But different people have different needs. I'm one of the biggest Linux fans in the world. However, I happen to think after reading the article that the writer would be better off using Windows.

    This is not because of l33tness, or because I want to be an asshole. The simple fact is that Linux is not yet ready right now for what our writer needs. The most distressing part of the article to me is that it took the writer 18 months to figure this out.

    The reason why no one has tried to make a *good* distribution is that the set of people capable of making distributions (call this set A) is not a representative sample of the population of people who need a *good* distribution. Members of set A tend to be just fine with using command lines and writing printer magicfilters.

    People often lose track of the following two points:

    1. This problem is *hard* to solve. It is a classic chicken and egg. You can't create a distribution until you enter set A, but by the time you've entered set A what's good for you is no longer what's good for average joe.
    2. There's no rush to solve this problem. People often fall into the trap of thinking that Linux has to grow in order to survive. But Linux is not like other commerical platforms. Linux is the most successful user-developed platform in history. Because Linux development is so open and accessible, Linux does not need popular success in order to thrive.
    While I certainly agree that Linux should suck less, I also don't think that Linux can be all things to all people. Some users really are better off not using Linux. In time this problem may be solved, but that hasn't happened yet.
  13. Re:Article Summary by Pyromage · · Score: 5, Insightful

    I'd like to clarify a few things a bit.

    I admit I was a bit (bit? Whatever... understatements are fun) negative in my original post.

    I mean to say that many people (not necessarily a majority, but more than 5) here on slashdot bash people for being stupid, for not knowing this or that random command.

    I just think it's in poor taste to flame the author of this article for not getting things to work. Or for not searching hard enough. Or for not having spare computers for internet access.

    I just mean to point out that the aforementioned part of the population writes these flames far too much.

    I apologize for ripping on the various distros so much; I meant only to illustrate that there isn't a distro out there that has a stated and executed goal of making a distribution that is genuinely good and that works well, for the average user (Say, the author).

    Slackware provides nothing. Perfect for me, but not our average user. Mandrake, Red Hat, SuSE, etc. all provide many useful tools, but they are too fragile. Debian has some things better, some worse.

    The reason I mention debian is important: the optimal distribution for the average user doesn't provide 10000 packages, like Debian does.

    It provides a few packages, maybe a couple hundred, that have been reviewed, checked, and polished. That don't crash. That are well documented. That do the job. Why not include the best 2 products for a task, that have been looked over first and polished to perfection, rather than just shoving in many others that halfway do the job?

    I think the author is presenting an exaggerated view, because of her perspective. That's OK: it's a relatively average user's perspective. I just get annoyed when her exaggerations are flamed by slashdotters that exaggerate as much in the other direction. Nothing personal, but seriously folks, think before you insult.

  14. Re:It's not a matter of lots of money by Osty · · Score: 5, Interesting

    Putting

    - It's made by developers for developers

    and
    So, why not one good interface?

    together makes one wonder, what developers was (because like it or not, the various Linux distros are trying to target Joe Sixpack-type users these days) Linux trying to target? There are essentially three types of developers in the world, with variations on each:
    • The casual developer. This guy likes quick&dirty tools, because he's focused on getting the job done. RAD environments like VB or Delphi make it easy for this developer to get his work done with a minimum of fuss. He doesn't spend time thinking about development issues or reading books to learn esoteric (to him) ideas. He pops open his RAD environment with a specific goal, throws together a form that does something (reads data, munges it, spits it out on a form), and is done. I'd say this is the most common developer out there, and thus is why VB and Delphi are so popular. I'd say this group also includes your average sysadmin, if you consider scripting languages to be RAD tools.
    • The professional developer. This guy is competent, and likes a job well-done, but isn't obsessive-compulsive over having the cleanest or most elegant solution. He's usually writing code under deadline pressure, and it's more important that it works than that it's clean. These guys usually write in Java, .NET languages like C#, or C++, though they often use other languages like SQL or various scripting languages to support their work. The professional developer likes a good IDE, because it helps him get his job done, but he can get by without it holding his hand. He'll often buy books and learn new technologies. These guys are less common than the casual developer.
    • The hardcore. This includes researchers and the unix-style system programmers. It doesn't matter if it took ten years to ship their product so long as it's elegant and clean. They're obsessive-compulsive about their development environment, and will rage on and on over their choice of editors. These are the guys you'll find in protracted debates about emacs or vi, while everybody else is using neither. They like low-level languages, usually C though some use C++ without being ostracized. They're also fairly uncommon outside of a University setting.

    It seems to me that the last developer type is what Linux is targetting. Maybe it's a little short-sighted to target the least-common of developer types?

    Regardless, all of that is more or less a red herring today. As I mentioned above, nearly every distro is moving towards one of two things (or both, in the case of Redhat) -- they're targetting servers, or desktop users. The hardcore developers don't really matter, because they know how to get all the tools they need if they're not distributed with the system, like you mentioned. The other types are more or less ignored -- there's no real RAD solution under Linux other than Kylix, and there's no single, coherent object model or set of interfaces (I just re-purposed the word "interface", because while I know you meant "user interface", I think it should also apply to programming interfaces) for writing software (there's GNOME, KDE, GTK, Qt, GNUStep, etc, none of which are guaranteed to be available for any given end-user, so they either have to make a conscious choice to exclude potential customers, or take pains to make sure the neccessary depenedencies are available at install time).

  15. Re:Article Summary by harriet+nyborg · · Score: 5, Insightful
    "I think the author is presenting an exaggerated view, because of her perspective. That's OK: it's a relatively average user's perspective."

    i like skiing.

    i've tried snowboarding, but for me, it's about as much fun as watching paint dry.

    funny thing is that despite my opinion about snowboarding, lots of other people seem to really dig it.

    no shit.

    you see them all over the place, wasting their time on those miserable snowplows when they could be skiing.

    sitting on their asses at the top of every run.

    slogging along on the cattracks like wounded animals.

    to a skier, you could think of them as the lowest form of life.

    or you could notice that these worms pump money into the lift systems.

    and force "ski" areas to change their way of thinking.

    i credit these scumbags with the phenomenal expansion of back country skiing in america. 10 years ago you couldn't cut through the woods without getting your ticket clipped, but today most mountains are opening up their backcountry. it is the biggest advancement of liberty since the signing of the declaration of independence. a fucking revolution (excuse my french.)

    now i'm off piste.

    my point is that the author's "exaggerated view" is more distored than exaggerated. she's a skier who got on a snowboard and got pissed off and frustrated when she couldn't turn. she wants to do all the same things she can do easily on skis, but no matter how hard she tries, snowboarding puts her on her ass.

    instead of complaining that snowboarding is not skiing, she should get back on her skis and thank all those dirtbag snowboarders for making skiing a better experience.