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."

Comments

Re:Brief comment

[richi]

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.

Linux printing is a nightmare.

[SlashChick]

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,