TTG Home   » Robert Home » Linux Chronicles for April 2002
Photograph of Robert Bruce Thompson
Linux Chronicles

April 2002

Latest Update : Tuesday, 23 April 2002 9:45 -0400





Click Here to Subscribe
Messageboard
Daynotes Journal
Visit Barbara's Journal Page




Monday, 15 April 2002

The computer formerly known as thoth (my previous main system) has been reincarnated. It's now known as galileo and is running a kitchen-sink install of Red Hat Linux 7.2.

This is the machine that had started locking up on me for no apparent reason. My guess was that it was filthy inside and was overheating, and that turned out to be the case. From the outside, the system didn't appear that bad. There were a few dust bunnies visible around cracks in the case, on the power supply grill, and so on. But in general the system looked pretty clean.

Until, that is, I opened it up. While Barbara was vacuuming the house yesterday, I carried old thoth into the kitchen and popped the lid. The internal power supply grills were covered solidly with dust, as were the expansion cards, memory modules, and processor. In fact, the processor was covered in so much dust that the CPU fan may have been jammed. It's a slot 1 Pentium III/750 (well, really, it's a Pentium III/733 with a 133 MHz FSB, but it's an unlocked engineering sample, so I'm running it in the 100 MHz SE440BX-2V motherboard with a 7.5X multiplier for 750 MHz). The processor has a heavy aluminum heat sink attached to the case, with a small fan held on by four screws that simply wedge between the fins of the heatsink. I removed the processor from the system and pulled off the fan. There was so much dust in there, I suspect it may not have been able to spin very well if at all. The portion of the heatsink underneath the fan was so clogged with dust that even had the fan been running it can't have been doing much cooling.

So I cleaned everything out, pulled all the PCI expansion cards, and gave everything a good dusting. While I was at it, I decided to replace the memory. I had thought the system had 256 MB, but as it turned out it had only 192 MB, a 128 MB Crucial PC100 DIMM and a 64 MB Crucial PC100 DIMM. I figured those were probably okay, but since I had the case open I decided just to pull them and install two 128 MB Crucial PC133 CL2 DIMMs. I was thinking about installing more, but this system is destined to become my production Linux server, and 256 MB seemed sufficient.

For now, I'm playing around. Before long, I'll be getting serious.


Tuesday, 16 April 2002

I have spent a bit of time playing with Linux. I downloaded and installed Ximian Red Carpet, subscribed to the Red Hat 7.2 channel, and told it to download all the updates available. There are more than 200 of them totaling 358 MB. I'm sucking those down now, at 120 KB/s. I have no idea what most of them are for, but I suppose I need them. The next thing I need to do is get Samba set up so that my Linux system can see my Windows systems and vice versa.

I'm going to keep my main Windows 2000 desktop as a crutch until I'm comfortable with Linux. That'll come as I get comfortable with Linux on my secondary desktop system. As that happens, my secondary system will gradually become my primary system. At some point, I'll also take down the Windows system in the den and replace it with a Linux box.



14:45 - I've said all along that my transition from Windows to Linux would be a gradual process. At first, I'd use my main Windows system 90% of the time and my main Linux system only 10% of the time. Gradually, that proportion would be reversed, and I'd be using my main Linux system almost exclusively. I started working with my Linux desktop system yesterday afternoon. It's been a long struggle, but I think I'm almost ready to make my Windows desktop my secondary system and start using my Linux desktop as my primary system. There are a few things I need to do before I can complete the transition, to wit:
  1. The big one first. I still haven't been successful in accessing my Windows Networking systems from the Linux system, or vice versa. I need to be able to view Windows shares on my Linux box and vice versa . In the KDE Control Center, there's an option called Network -> LAN Browsing, and another called Windows Shares. Can it really be as simple as configuring those dialogs correctly?
  2. I have a DDS-3 tape drive in the Linux box. It would be nice to be able to backup my local system (and, ideally, shares on the Windows network) to that tape drive. Is there a graphical backup application somewhere on my Linux system that I'm missing? I do vaguely remember from the distant past using tar to archive stuff to tape, but I'm hoping there's a tree-structured graphical backup app I can use to archive data to my tape drive.
  3. I know there are front-ends for burning CDs. This system has a 12X Plextor writer in it, but I'm not sure how to burn CDs. Any tips greatly appreciated.
There are probably other things I'm overlooking, but these are the main ones for now. I've loaded Ximian Evolution and am able to send and receive mail. I have my real mail store on a Windows box (using Mozilla Mail) right now, so I've told Evolution to leave a copy on the server. Once I get #1 above resolved, I'll move my real mail store over to the Linux box and import it (if necessary) into Evolution. I haven't downloaded OpenOffice for Linux yet, but I've run it on Windows and I'm sure it'll be adequate for what I need to do. Worst case, I'll always have a Windows system running with Office 2000 on it, so weirdly formatted documents shouldn't be a problem.

It seems that I'm on my way to running a Microsoft-free computing environment. And it seems that it's not as painful as I feared it would be. There are pitfalls, certainly, and things I haven't figured out how to do yet. But I'm confident that I'll work my way past those, with a little help from my friends. And I'll be cheating now and then, when there's something I absolutely need to do and haven't figured out how to do in Linux yet, or when I need to run an application like Cartes du Ciel that is available only for Windows. But those Windows systems are now largely just crutches. I know they're there if I need them, but I probably won't need them much.

Now, where do I get those penguin stickers to put on the front of my computer cases?


Wednesday, 17 April 2002

I'm in the process of converting over to Linux entirely. Thanks to Greg Lincoln, who solved my major problem, at least in part. I wasn't able to access Windows shares from my Linux system. Here's what Greg told me to do:

Hi Bob,

Brian and I worked on your big three a bit, and here's what we have so far.

1. LAN browsing in KDE seems to be pretty straightforward. What we've not
figured out yet is how to get write access through KDE's smb browsing. To use
the read only bit, just open a konqueror window and type smb:/MACHINENAME/
This will only work if you have samba-client installed, which I believe is
installed by default in redhat.

If you want write access too, the only way we've found is to mount the shares.
You can make entries in your /etc/fstab file to automate this. Here is the
syntax: (*all on one line, the mail client wraps it*)

//machine/share /path/to/dir/ smbfs
username=smbusername,password=smbpassword,uid=bob,gid=bob

//machine/share = the servername and the sharename
/path/to/dir/ = the directory on your linux machine to which you wish to
mount it (I suggest you create a directory in your home -> /home/bob/share)
uid=local user to whom you want to map the permissions
gid=local group to whom you want to map the permissions

2. The best cd writer front end I've found is part of KDE 3 so it won't be in
your redhat install, alas. gcombust is pretty good. You will probably have to
install some of its dependencies.

http://mirrors.kernel.org/redhat/redhat/redhat-7.1-en/powertools/i386/RedHat/RPMS/gcombust-0.1.37-2.i386.rpm

3. I'm not sure if it ships with kde 2, but kde 3 has a nice tar GUI called
kdat. It shows up in my k -> utilities menu. It seems to be well documented,
like most kde apps.

--
Greg Lincoln
Senior Editor, LinuxHardware.org
http://www.linuxhardware.org

Which indeed works, but only on Windows NT 4 shares. When I attempt to do that for Windows 2000 shares, I get the following error message, both at boot time and when I try to access the share:

Could not mount device.
The report error was:

mount: only root can mount //messier/messier_c on /home/thompson/share/messier_c


I tried the same thing on other Windows 2000 shares and got the same results. Apparently, Microsoft changed something in Windows 2000 that breaks SAMBA. But that will do, at least for now. I can access my server volumes on theodore, and that's all that really matters.

Right now, I'm running my mail on three different clients with three different mail clients. Until a few minutes ago, I had Mozilla Mail running on messier (my main Windows desktop) set to POP from my server at pair and delete the messages after it retrieved them. I have Evolution running on galileo, also set to POP from pair Networks, but to leave messages on the server. I have Outlook 2000 running on ursa (my Windows 2000 system in the den), also set to POP from pair Networks and leave messages on the server. My main mail store is therefore on messier. I can't figure out how to point Mozilla Mail to a different directory, so I just let it store the mail locally on messier and periodically manually copy and paste the whole mail directory hierarchy over to theodore (the Windows NT 4 Server file server), from which it gets backed up.

I intended to make Evolution my primary mail client last night, and so attempted to import the Mozilla Mail data into Evolution. That didn't work as expected. I ran the import utility and was given the choice of importing all data from an older mail system or doing a file-by-file import. When I chose the first option, I was presented with a blank screen. No joy there. Just to experiment, I told Evolution to do a file-by-file import and pointed it to the Inbox file. That worked fine, so I shouldn't have any problem importing my data, except that I'll have to do it folder by folder (and I have many, many folders). Also, I'm not sure how I'll get my non-mail folders (such as my contacts) into Evolution.

What I considered doing was setting up Mozilla Mail under Linux and then copying all my Mozilla Mail data over from messier to galileo . Presumably that would allow Mozilla running under Linux to see all that data and then subsequently allow Evolution to import it as a batch. The only problem is that I can't make it work. Oh, well. At least I can get my messages over to Evolution, and I should be able to import my addressbooks somehow.



Holden Aust sends me very detailed instructions for burning CDs under Linux. Although it's a long message, there's so much valuable information here that I decided to post his message in full so that I and others can refer to it later.


Bob,

This is somewhat of a mismash (that I've been meaning to clean up one of these days when I have time, of course) that I've put together from bits and pieces I've run across here and there.

Much of it is at a fairly elemental level since I give it to friends who are going nuts trying to get their CD recorders to work consistantly under Windows - I've actually had half a dozen friends ask me to setup a Linux dual-boot partition for them just so they could use Linux to make CDs reliably.

I've experimented somewhat with Xcdroast and KonCD, but I'd have to admit that the GUI front ends for the Linux command line CD recording utilities are primative compared to Nero (we should all bug Nero to come out with a Linux version - I'd bet a lot of people would pay for one - I would).

But, once I figured out how to use cdparanoia and cdrdao and readcd and cdrecord, I stopped worrying about GUI front ends, because using the command line utilites is easy and they work really well.

Here begins the mismash:

Some basic shell prompt command line commands (press ENTER to run the command):

pwd Print Working Directory (this shows you what directory you are in)

cd <directory name> Change Directory down the tree to a directory under your current directory that is called whatever you type after cd (don't type the < >, just the directory name)

cd .. Backs you up the directory tree one level (i.e., if you are in /images/Bach and you want to go back to /images)

md <directory name> Make Directory makes a directory under the current directory using the name that you typed after md (again, don't type the < >)

ls Lists the files and directories in and under the directory you are currently in

rm *.wav deletes all files with a wav extension in the current directory

rm *.toc deletes the audio-cd.toc file in the current directory

rd <directory name> Remove Directory deletes a directory (only if the directory is empty)


******************************************************************
Depending upon how the rights (permission to use specific programs) are setup, you may have to be logged in as the "root" superuser to be able to run the programs listed below.

Sometimes you may be able to login as your normal user and specify that you need to have the ability to run programs that the root user has. To run the following commands, you need to be logged in as the "super user" with equivalent powers as the "root" user. To do this, open a "Shell Prompt" by clicking on the icon on the bottom of the screen that looks like a computer monitor with a shell (like the Shell Oil trademark) superimposed over the computer monitor. When the "Shell Prompt" opens, type the following:

su (Then press the Return or Enter key - you will then be asked for the root user's password)
(enter the root user's password and press the Enter key again - now you can use the following commands)

******************************************************************
In the examples below, where it may say device=0,0,0 or device=0,6,0 those are just examples and may not necessarily be the exact command for your system. To find out what the device number for your own CD recorder is, type this command and read the output on your screen:

cdrecord -scanbus


Also, where the commands indicate a speed, as in "--speed 4", put in the maximum recording speed of your specific CD recorder for the type of blank CDs that you are using (for example if you have an 8x4x32 CD recorder, you would use "--speed 8" if you are using CDR blanks and "--speed 4" if you are using CDRW blanks).

*******************************************************************


Read audio CDs using: cdparanoia -v -s -B "1-"

Write audio CDs using: cdrdao write --speed 4 --eject --device 0,6,0 audio-cd.toc

(Speed parameter and device 0,x,0 will vary with hardware setup, use cdrecord -scanbus to find out what the SCSI device ID number is)

If your original CD is scratched, you may want to slow down the reading process to try to correct for the errors by including a "-S 2" or "-S 1" on the command line for cdparanoia (-S 2 will read the CD at twice normal playing speed, while -S 1 will read the CD at normal playing speed). Since you are reading at either the normal playing speed or twice the normal playing speed, it will take longer to record a CD to your hard disk than it does using the normal reading speed, but if the CD is defective, you may have to do this to get an error-free read:

cdparanoia -v -s -B -S 2 "1-"


If your CD recorder is a new model, it may use a generic driver, so try one of the examples, below:

cdrdao write --speed 4 --eject --device 0,6,0 –driver generic-mmc audio-cd.toc

cdrdao write --speed 4 --eject --device 0,6,0 –driver generic-mmc-raw audio-cd.toc


Contents of the audio-cd.toc file which has to be in the subdirectory containing the wav files:

CD_DA



TRACK AUDIO

FILE "track01.cdda.wav" 0


TRACK AUDIO

FILE "track02.cdda.wav" 0


TRACK AUDIO

FILE "track03.cdda.wav" 0



Copying audio CDs and creating image files

cdrdao read-cd --device 0,0,0 audio-cd.toc



Copying data CDs and creating image files

dd if=/dev/scd0 of=datacd.img (of = output file)



Use readcd if there are so many errors that dd is not able to finish generating the image file

readcd dev=0,0,0 f=data-cd.img (of = output file)

gramofile is used to copy LPs, cassettes, etc. to an audio file


Use mkisofs to create an image file of any file or directories:

mkisofs -o <image file> -r -T -J <source directories>

mkisofs -o <home.img> -r -T -J /home /etc /usr/bin


Using cdrecord to copy data image files to a CD:

cdrecord -data -eject speed=4 dev=0,0,0 home.img


To use cdrdao to create a data CD, you need to create a data TOC:

CD__ROM


TRACK MODE1
DATAFILE "home.img"


cdrdao write --eject --device 0,0,0 home.toc


To compare an image file burned onto a CD to the original file:

dd if=/dev/cdrom test.img
cmp test.img original.img

This should produce NO output, which indicates it is a good copy. Music CDs can produce minor differences, but data CDs should not.



CD Copying

The following command will copy the CD in the source drive specified with option --source-device to the CD-R/CD-RW inserted in the destination drive specified with option --device. Only a single session will be copied which can be selected with option --session (default: 1st session). If you want to keep the session open you will have to use option --multi.

cdrdao copy --source-device 0,2,0 --device 0,5,0 --buffers 64

The option --buffers is used to adjust the ring buffer size. Each buffer holds 1 second audio data. Dividing the specified number of buffers by the writing speed gives the approx. time for which data input my be stalled, e.g. 64 buffers and writing at 4x speed results in 16 seconds.

On the fly copying is selected with option --on-the-fly. No intermediate data will be stored on the disk in this case.



cdrdao copy Copies from the CD recorder to the CD recorder


cdparanoia -v -s -B -S2 "14" Reads track 14 at speed 2x


-d --force-cdrom-device device
Force the interface backend to read from device
rather than the first readable CDROM drive it
finds. This can be used to specify devices of any
valid interface type (ATAPI, SCSI or proprietary).





To solve this problem, instead of two copies of fstabs, simply delete the soft link file /dev/cdrom and type ln -s /dev/sr0 /dev/cdrom. This creates a new link file pointing to the new cdrom device as create under ide-scsi driver. If all you have is one (scsi) cdrom (emulated or real) in your linux system, it usually should be /dev/sr0.


Lilo commands if you have trouble installing Linux: disableapic ide=nodma pci=biosirq hdc=serialize (for old CDROM drives, if CDROM is hdc)


3979: How to Burn CDs With cdrecord
On the Solaris[TM] 8 Operating Environment
URL: http://www.sun.com/software/solaris/freeware/download.html

You can use cdrecord, a simple command line program, on the SolarisTM Operating Environment to duplicate existing CDs or to make CD data backups of hard disk files.

Burn CDs With the SolarisTM 8 Operating Environment

CD-ROM drives are commonly used for duplicating existing CDs, and for
making CD data backups of hard disk files. This article demonstrates
how both tasks can be accomplished using cdrecord on the SolarisTM
Operating Environment.

A simple command line program, cdrecord, means burning CDs using
Solaris software is quick, simple, and cost-effective. The cdrecord
program, which works for both SPARCTM and Intel Architecture systems,
is included on the Solaris Software Companion CD (Update 2 and higher),
and is also available for free download from

http://www.sun.com/software/solaris/freeware/download.html

www.sun.com/software/solaris/freeware/download.html

While optional, configuring a cdrecord startup file,
/etc/default/cdrecord, will save time in the future. This startup
configuration file can hold information that cdrecord will need every
time it's used, such as the CD recorder's speed, device name, the
preferred buffer size, and so on. Alternately, these options can be
entered into the command line before every use.

The first step is to identify the cd recorder device name, which can be
found by scanning the device buses. In order to scan the devices,
however, the volume management must be turned off.

- Log in as root

- Turn off volume management by typing /etc/init.d/volmgt stop

- Discover the CD recorder and CD-ROM drive device names by typing
cdrecord -scanbus at the root prompt. The command output should be
similar to:

# cdrecord -scanbus
cdrecord 1.9 (i386-pc-solaris2.8) Copyright (C) 1995-2000
1,0,0 100) 'CREATIVE' 'CD5233E ' '1.00' Removable CD-ROM
2,4,0 204) 'PLEXTOR' 'CD-R PX-R820T' '1.05' Removable CD-ROM

The device ID is the first three numbers listed in each entry -- in
this case, device 2,4,0 is the CD recorder, for example. The
configuraiton file can also include a recording speed (for example, 8
times), and a buffer size (for example, 8 megabytes) to help avoid
under runs. To create the configuration file, located in
/etc/default/cdrecord, type:

# cat /etc/default/cdrecord
CDR_FIFOSIZE=8m
CDR_SPEED=8
CDR_DEVICE=USCSI:2,4,0

The cdrecord program startup configuration file is now set up for the future!

CD to CD

To duplicate an existing CD, insert the CD into the CD-ROM drive.
(Remember, duplicating CDs might require certain copyright and license
permissions!) Then:

Determine the controller and target numbers. These are listed in the
cdrecord -scanbus output (from before): 1,0,0 100) 'CREATIVE' 'CD5233E
' '1.00' Removable CD-ROM . The first number is the controller number,
and the second number is the target number. In this case, they are one
and zero, respectively. Also note that in the Solaris 8 platform, the
IDE CD-ROM drive device names are very similar to SCSI device names --
both contain target numbers.

Choose an output file with sufficient free hard disk space (at least
700 megabytes recommended). For this example, the free space is located
in the /local file system.

Capture an ISO image file of the CD by typing (at root prompt):

# dd if=/dev/dsk/c1t0d0p0 of=/local/mycdromfile.iso

It will take about five to ten minutes to copy the entire CD image file
to disk. After inserting a blank CD into the CD-ROM drive, burn the
image from disk onto a second CD by typing:


# cdrecord -v /local/mycdromfile.iso

This should take about 15 to 30 minutes, depending on the speed of the
CD burner. In the above command, -v displays each step with extra
information, just in case something isn't successful.

Data to CD

Many users also utilize CD-ROM drives to create data backups on CD of a
system's home directory and files. The Solaris 8 Operating Environment
includes a very useful command for this, mkisofs, which creates an
image file when pointed at a system directory. To make an image file of
a home directory, for example /home/neal, type:

# mkisofs -l -L -r -o /local/mycdromfile2.iso /home/neal

This will take all the files in the /home/neal directory and create a
CD-ROM ISO image file at /local/mycdromfile2.iso.


When this is finished, insert a blank CD into the CD-ROM drive, and type:

# cdrecord -v /local/mycdromfile2.iso

This will copy the data image onto the blank CD, and should take about
15 to 30 minutes depending on the speed of the burner. More information
about the mkisofs command, including all its configurable options, can
be found by typing man mkisofs at a shell prompt.

For additional software and hardware information, documentation, source
code, and a list of supported CD recorders for cdrecord (an open source
project), visit the Freshmeat Web site.

http://freshmeat.net/projects/cdrecord


Copy a CD by:

cdrdao copy --device 0,0,0



Thursday, 18 April 2002

9:20 -
I'd intended for today's entry to be the first one done completely under Linux, but that turned out not to be possible.

I've made a fair amount of progress. My primary mail client is now Evolution running on my Linux box. It's by no means as full-featured as Outlook 2000, but it seems to have all the essentials. I'm really looking forward to Evolution 1.1 or 2.0 or whatever they call it. There are a lot of convenience features that need to be added, and my guess is that the programmers are working on them for the next major release. But Evolution is Good Enough for now.

Among the features they really need to add is a usable Outlook import facility. Mozilla mail imports Outlook messages and address books, so there's no reason why Evolution can't do the same. It is, after all, aimed at the corporate Outlook market, so it's pretty much mandatory that it be able to import data from the application that it's intended to replace. Instead, the current release of Evolution says that it can't read Outlook files, and actually recommends using Mozilla Mail as an intermediary to get Outlook messages into Evolution.

The Outlook-to-Mozilla part works great. Mozilla's import grabs Outlook messages wholesale and puts them (and the folders that contain them) in a separate set of "Imported Mail" folders in Mozilla. It goes downhill from there, though. As far as I can see, there's no way to bulk import the mail from Mozilla to Evolution. Instead, you have to import it folder by folder. That at least does work properly, but it's quite time-consuming to replicate the Outlook/Mozilla folder structure in Evolution and then import folder by folder into Evolution.

What's worse is that there is apparently no way to import address books into Evolution. The best Evolution can come up with is to suggest mailing your contacts to yourself. I couldn't come up with any convenient way to do that in Mozilla, so I fired up Outlook, selected every contact in my Contacts folder, and sent them all as one huge mail message. That arrived in Evolution fine, but there was no way I could find to extract that data from the message and put it into Evolution.

So I decided to try sending my contacts one-by-one as v-card file attachments. Actually, I had too many contacts, so I decided to use my Subscribers list instead. I tried mailing one subscriber record as a vcard, and that worked fine. I opened the message in Evolution, and there was a button at the bottom of the message that said "Add to Addressbook" or something similar. Fine. So I spent the better part of an hour emailing each Subscriber record as an individual v-card attachment. Only after I'd sent them all and retrieved them in Evolution did I learn that the process didn't go as smoothly with most records as it did with that first test record. Evolution did in fact import the v-card data, but the resulting records were incredibly ugly. Each of them took up a full column in Evolution's Contacts display, with lots of little boxes and strange characters in the Notes fields.

After that, I tried everything I could think of, including exporting my Contacts records as comma-separated-value ASCII files. Nothing I tried worked. In each case, Evolution told me that it didn't have an importer for the format I'd chosen.

At that point, I decided to pend getting my contact data over to Evolution and move on to something else. Apparently, I lost my mind, because I decided to upgrade my system to KDE 3. (I should mention here that any bad things I say in this or future journal entries about stuff that happens is not criticism of the people who are helping me. It's pointing out that I do these silly things because I'm silly.) Greg Lincoln had sent me a link to the site where I could download the rpm's for KDE 3 stable for Red Hat 7.2. I went to that site and downloaded, as Greg suggested, every file I found there except the language support files. I don't need support for Croatian or Norwegian or any of the other languages, but I did grab everything else.

I stuck the downloaded files in the /home/thompson/kde3 directory. Once I had them all, I brought up a command prompt window, executed su to make myself super user, changed to the /home/thompson/kde3 directory, and used the command rpm -Uvh *.rpm to install KDE3. Being an optimist, I was at that point expecting the process to complete normally and give me KDE 3.0. Instead, I got a whole bunch of error messages about failed dependencies. Oh, well. Everything seemed to continue working normally, so I assumed that the rpm installer was smart enough to check for dependencies before doing anything to the existing installation. That seemed to be the case, and everything continued working normally.

So I continued playing around with various Linux stuff, planning to ask Greg later what if anything I should do about KDE 3. It was then that I decided I was going to use Linux to do this page for tomorrow (today). Planning to use Mozilla Composer, I fired up Mozilla. Big mistake. It appeared to start normally, although with the ugly old Netscape skin. I clicked on Task - Composer and Composer came up apparently normally. I called up this page, which is located on the Windows server, and it came up, apparently normally.

Then I got to thinking about version numbers. I'm running 0.9.9 on Windows and wasn't sure what I was running on Linux. So I made the big mistake of clicking Help -- About. That brought up a new Navigator window and locked Mozilla up tight. All of the Mozilla windows were still visible, but none of them responded to any commands, including my attempts to close them. I searched in vain for an equivalent to Windows' Task Manager -- End Task command. Mozilla was covering my desktop and wouldn't go away. I couldn't move, minimize, or close the Mozilla windows. What was worse was that if I started another program like Evolution or Solitaire, the resulting program window was underneath the frozen Mozilla windows. I could of course get a fresh desktop by clicking 2, 3, or 4 down on the task bar, but nothing I did would fix the frozen windows in my primary desktop.

Eventually, I rebooted the system. The Mozilla windows were still there, but I was able to close them. So I took the Gone With the Wind approach, and decided to think about that problem tomorrow. As I was using Evolution, I made the mistake of clicking on a link embedded in an email. Instead of firing up Konqueror, Mozilla came up. I'm not sure how or why Mozilla ended up associated with html files and I really wish I knew how to change the association back to Konqueror. Because each time I click on an embedded link, Mozilla comes up and freezes.

So I decided to upgrade Mozilla to the current version. I used Konqueror to go over to the Mozilla web site. I found the rpm for Mozilla 0.9.9, downloaded it and double clicked on it to bring up the GUI rpm installer. I told it to install the 0.9.9 version, but again I got a failed installation due to a bunch of dependencies. Obviously, I needed more than just the one rpm. There were a half dozen or more, but I foolishly assume that just the one 10 MB one would be sufficient. Obviously it wasn't.

There was also a tarball version that was a bit larger, but I didn't get it because I don't remember the procedure for extracting and installing from a tarball. I seem to remember from the hazy distant past that I'd need to download the tarball, run tar -xvf to unzip the files, do a chmod, and then execute an installer executable. Or something like that. But vague recollections from years ago aren't good enough. Come to think of it, it may even have been a .gz file rather than a tarball.

So I went back to download the rest of the Mozilla rpm's. I got all of them downloaded, fired up a command prompt, became superuser, changed into the download directory, and typed rpm -Uhv *.rpm. This time I got only one failed dependency: "mozilla = 0.9.2.1 is needed by galeon-0.11.3-2". So again there's no joy. I can see that failed dependencies are going to be very aggravating.

When I went to bed last night, my primary desktop was still cluttered with Mozilla windows-that-will-not-die. This morning, they're all gone. Very strange. At any rate, that's why I'm typing this in Mozilla 0.9.9 Composer on my Windows 2000 system.

13:00 - more in, including several helpful emails, which I reproduce here.

From:     Roland Dobbins
To:     thompson@ttgnet.com
Subject:     How to kill things.
Date:     18 Apr 2002 07:17:38 -0700   

I don't use KDE, but under most window managers, if you right-click on
the top frame of the application, you'll get an option to kill the
thing.

Failing that, open up a terminal, do a ps -ef | grep appname, then kill
all occurences thusly:

mordant@anabasis:~$ ps -ef | grep galeon
mordant  11959 11942  3 07:08 tty1     00:00:15
/opt/gnome/bin/galeon-bin
mordant  11966 11959  0 07:08 tty1     00:00:00
/opt/gnome/bin/galeon-bin
mordant  11967 11966  0 07:08 tty1     00:00:00
/opt/gnome/bin/galeon-bin
mordant  11968 11966  0 07:08 tty1     00:00:00
/opt/gnome/bin/galeon-bin
mordant  11969 11966  0 07:08 tty1     00:00:00
/opt/gnome/bin/galeon-bin
mordant  11971 11966  0 07:08 tty1     00:00:00
/opt/gnome/bin/galeon-bin
mordant  12107 12095  0 07:15 pts/0    00:00:00 grep galeon
mordant@anabasis:~$ kill 11959 11966 11967 11968 11969 11971 12107

or

mordant@anabasis:~$ killall galeon-bin

Thanks. As it turned out, I didn't need to kill the steenking processes. Instead, I killed the whole application (along with Evolution, which I didn't want to kill. I got it back, though. More later on my page.

And more from Roland, this time about RPMs:

From:     Roland Dobbins
To:     thompson@ttgnet.com
Subject:     RPMs.
Date:     18 Apr 2002 07:20:53 -0700   

http://www.tfug.org/helpdesk/linux/rpm.html
--

Which indeed turns out to be a useful summary page for learning how to use the Red Hat Package Manager. Too good, in fact. I remember years ago when I was trying to help a friend on the phone. He was having problems with, as I recall, Windows 3.11 for Workgroups. At one point during the conversation, he said "I wasn't sure what the file was for, so I deleted it." Duh. But then I did the same thing today. One of the segments in that page tells you how to delete packages without consideration for dependencies. The author warns the reader that doing so can have very bad results.

I was getting a bit frustrated with my inability to upgrade Mozilla. The first thing I did was try to delete Mozilla. That refused to work because Galeon required one of the Mozilla 0.9.2 files. So I deleted Galeon. So far, so good. Then I tried running an upgrade of Mozilla to 0.9.9. No joy. So I decided to delete Mozilla, which worked fine. I then tried to install Mozilla 0.9.9. That failed, because one of the RPMs in my mozilla-0.9.9 directory was mozilla-nss-0.9.9-0. RPM informed me that mozilla-nss-0.9.9-1 was already installed, and aborted the installation of Mozilla. Okay. Time to delete mozilla-nss-0.9.9-1. When I tried that, RPM told me that it was required by Evolution. Gulp.

Well, my mail was already backed up to a different system, so I went ahead and told RPM to remove mozilla-nss-0.9.9-1 without considering dependencies. That worked, of course, but it killed Evolution. Oh, my. So I installed Mozilla 0.9.9, which worked fine. Evolution was still dead, of course. So I fired up Red Carpet, intending to tell it to go get Evolution and reinstall it. That option wasn't offered. Okay, I fired up a terminal window again, su'd to root, and uninstalled my broken copy of Evolution. I then fired up Red Carpet again, and found that Evolution was now available to be downloaded. I told it to go ahead and do that. It did, and Evolution is now back up and running with no loss of data. And Mozilla 0.9.9 works.

I'm impressed at how robust Linux is. Doing something like this with Windows would probably have trashed everything beyond hope of recovery. But Linux just keeps on ticking.

So now I have Evolution and Mozilla 0.9.9 both working fine. I'm writing this on my Linux box. What is truly strange is that Mozilla Composer got everything off my Windows box without being told. That is, when I fired up Mozilla Composer for the first time, it already had the same most-recently-used list of files and so on. The only place it could have gotten them is from the Windows box. I have no idea how it did this, but it's very nice.

One thing that's not so nice is the ugly fonts. I know that there's some sort of issue with TrueType, although I'm not aware of the details. In fact, the Mozilla download page specifically says that there's no TrueType support. I believe this is a licensing issue, but I don't understand why it's a problem. After all nearly everyone has a full set of licensed TrueType fonts around on a Windows CD somewhere. If I'm not using that Windows copy, should I not be able to just stick the CD in my Linux box and have it use those already-licensed fonts?

I'm also not sure why some applications seem to be using pretty fonts and others ugly ones. At first, I thought it was KDE versus Gnome, because Evolution looks very pretty. But then I noticed that some KDE stuff doesn't seem to have the ugly fonts problem. This would be a good thing to figure out. The fonts are usable as-is, but they are indeed ugly. I don't think I'd want to be forced to look at them all day long while I work.


Friday, 19 April 2002

I haven't done much with Linux since my last post (other than use it to get work done), but there is some good mail I wanted to get posted:

From:    Bob Willoughby
To:      thompson@ttgnet.com
Subject: Backing up to CDs
Date:    17 Apr 2002 18:49:22 -0500   

For another take on backing up to cd's in linux, this article is in the HOWTOs of LinuxOrbit.com:

http://www.linuxorbit.com/modules.php?op=modload&name=Sections&file=index&req=viewarticle&artid=222

The article is titled, "Backing up to CDs Made Simple: Version 1.1.  I haven't tried it, but the writeup seems straightforward to me.  Oh yeah, the article is long, but it has a printer friendly button thatn produces text which prints out nicely.

You may be past this point by now, but perhaps this will help.

Ciao.           ...bob

Then Phil Hough and Mike Strock weigh in on using SAMBA with Windows 2000 shares:

From:    Phil Hough
To:      Robert Bruce Thompson <thompson@ttgnet.com>
Subject: SAMBA and Win2K
Date:    17 Apr 2002 18:03:18 +0100   
 
"I tried the same thing on other Windows 2000 shares and got the same
results. Apparently, Microsoft changed something in Windows 2000 that
breaks SAMBA. But that will do, at least for now. I can access my
server volumes on theodore, and that's all that really matters."

It can be done... I've got my Redhat 7.1 (non-upgraded at all) box
backing up shares from my Windows 2000 machine, and able to write to
shares on it if I like (just tried it).  And likewise I can read and
write to Linux shares from Windows 2000 without a problem. 

I didn't do it the easy way, but instead tinkered with the smb.conf
file by hand until it worked.  It took a while but I got there in the
end.  I can send you my conf files, and details of what I tinkered
with if you want, but I suspect you're looking for a slightly easier
way of doing it.   One tip though, one of the most important things I
learned was that you needed to let Linux know about the users on the
Windows 2000 box (you need to setup and account on the linux box if
you're reading from it, with a u/p that Win2k will use, and vice
versa, supply the u/p of the win2k account when accessing it).

I'm no world expert on this, just got there after much tinkering, but
if I can help, I will.

ATB.

Phil

And

From:     Mike Strock
To:       webmaster@ttgnet.com
Subject:  Samba shares thoughts...
Date:     17 Apr 2002 22:44:50 -0700   

Just a thought on your issue with writable Samba shares.  I hesitate to email
you, mainly because I'm a Windows guy, looking at Linux as an alternative
(not a Guru like Brian, GregL and the almighty Tom Syroid), but this is the
line I use to connect from my Linux laptop to my Win2k Server box, which
allows me to either read or write from /root/foo

mount -t smbfs -o username=administrator,password=<admin password> //192.168.2.28/f$ /root/foo
 (this should be on all one line)

This connects to the F$ administrative share on a Win2k Server on my local network. 

Is it perfect?  No.  Does it work?  Absolutely.

Don't know if it helps.  I hope that it does.

Mike Strock
http://www.myhomeoffice.org/ - New pictures of my kids here!

And Dave Markowitz tells me how to kill hung programs:

From:    Dave Markowitz
To:      Robert Bruce Thompson <thompson@ttgnet.com>
Subject: xkill in Linux
Date:    18 Apr 2002 16:42:04 -0400   

Robert,

Here's an easy way to kill locked programs if you are running X.

In KDE, if a program locks up, press ALT+F2.  This brings up the Run Command
dialog.   (Like Start > Run in Windows.) Type "xkill"  (all lowercase) in the
box.  Your cursor will turn into a little Jolly Roger, which you can then
place on the offending app, left-clicking once on it, thereby killing it. 

This is basically equivalent to issuing the "kill -9 <process #>" command at
a shell prompt.

If you accidentally invoke xkill, you can dismiss it by RIGHT-clicking
anywhere on your desktop, without killing anything.

HTH and welcome to the Light Side.  :-)

--
Dave Markowitz                  AIM: frodo527
http://www.building-tux.com     RKBA = FREEDOM!!!

Roland Dobbins and Greg Lincoln tell me how to use TrueType fonts in Linux:

From:    Roland Dobbins
To:      thompson@ttgnet.com
Subject: XFree86 Font De-Uglification HOW-TO.
Date:    18 Apr 2002 20:33:21 -0700   

http://www.tldp.org/HOWTO/mini/FDU/

and

From:    Greg Lincoln
To:      Robert Bruce Thompson <thompson@ttgnet.com>
Subject: fonts
Date:    19 Apr 2002 07:38:41 -0400   

Hi Bob,


Have a look at:

http://kb.redhat.com/view.php?eid=215

This explains how to get your Windows truetype fonts going in Linux. It looks
to make it a bit more difficult than it needs to be as it takes into
consideration every possible thing that could go wrong. For example, it walks
you through setting up xfs if it isn't installed, but it almost certainly is.

Once you get these going in X, they'll be available to Mozilla too. Mozilla
looks considerably better with truetype fonts, and it does support them. The
download page must have outdated information.

Let me know if you have any questions.

Also, kde 3 has a nice GUI tool that does the above process. =)  You can get
KDE 3 installed by installing the packages it complains are missing. You can
probably find most of them on your Redhat CD or at rpmfind.net. If you use
rpmfind, be sure you get rpms intended for x86 and redhat 7.1.

--
Greg Lincoln
Senior Editor, LinuxHardware.org
http://www.linuxhardware.org

And Mark Huth weighs in on Linux versus Windows:

From:    Mark Huth
To:      webmaster@ttgnet.com
Subject: Linux vs windows.
Date:    18 Apr 2002 21:36:24 -0700   

Bob,


I'm following your "conversion" to Linux with great interest.  I'd invested
months and dozens (hundreds??) of hours in doing the same.  I still not
there.  You've got a better chance, you've got more expertise and you've got
more "people" resources than I.   You can ask experts for help and get civil
responses.  It has not been my experience that, as a group, Linux experts
are all that civil and Linux documentation is horridly uneven.

In some ways, if computers are a hobby and you can invest lots of time and
energy in configuring, tweaking, etc., then Linux may well be the way to go.

My product is patient care and documentation and until things are more
mature in the Linux world, I'm afraid that Windows has to be my tool of
choice.

mark

Linux certainly isn't for everyone yet, but it's getting there. Sure, the Linux world has its share of bigots, radicals, and true believers, but my experience with Linux people is that they're almost invariably friendly and eager to help. For every LinuxPunk out there who's eager to show us newbies what morons we are and how smart he is, there are 100 or 1,000 normal folks who are willing to extend a helping hand.

My impression is that that situation is getting better, not worse. In the early days, Linux was more of a cult, so it was much more common to encounter the type of behavior you mention. But Linux has now broken out into the mainstream, and the True Believers are now a much tinier percentage of Linux users (and experts).

As you say, I do have access to many true experts in Linux. That's one of the reasons that I'm keeping this journal. As a Linux newbie, I figure that many of the showstoppers I encounter will also be showstoppers for others trying to get started with Linux. As I document the problems I encounter and the solutions to them, I'm also creating what I hope will be a useful series of documents for others who decide to take the plunge.





Saturday, 20 April 2002

12:15 - Trying to install TrueType fonts for Red Hat 7.2 brought to mind a classic episode of M.A.S.H. The one where Hawkeye ends up having to defuze an unexploded bomb sitting right in the middle of the hospital compound. There he is, standing next to a huge bomb with his tool kit, with everyone else hiding in bunkers. Hawkeye has no idea how to defuze a bomb, but fortunately they have the field manual, which gives detailed instructions. Someone else--Trapper John, I think--has that manual in a bunker and is shouting out the instructions to him, and the exchange goes something like this:

Hawkeye: "Okay, I have the cover off. What do I do next?"
Trapper:  (reading from the manual) "Cut the red wire..."
Hawkeye: (snips wire)
Trapper: (turning page of manual) "after first removing..."

Which is kind of how I felt when I tried to use the Red Hat instructions for installing TrueType fonts.

This page seems to tell you everything you need to know to install TrueType fonts under Red Hat 7.2. If only that were true. Unfortunately, the instructions they give are wrong, missing required information, and out of order. Or at least it looks that way to me. The instructions begin:

Put your True Type fonts in what ever directory you want.  For example, /usr/share/truetype, then run chkfontpath like this:
chkfontpath -add /usr/share/truetype.
This will add the new font directory to your font path.

So I logged on as root, got to a command prompt, and did that. (They didn't bother to mention that many of the TrueType fonts I copied from my Windows directory won't work because they use capital letters in the filenames. But I learned about that later.)

There are some real problems with the instructions they give here. First, there shouldn't be a period at the end of the line. I figured that one out myself. Second, the syntax is wrong. When I typed chkfontpath -add /usr/share/truetype I got an error message. "-add" isn't a valid option. It should have been "-a". Okay, so I ran the command again, this time using "-a". Didn't work. Why? Because the information they give first you have to do second, and the information they give second you have to do first. Duh. Here's what followed in the instructions:

If you do not have xfs installed, you need to install it first. Put the new fonts in a directory. If you are installing Type1 fonts, prepare the new directory for the server by running type1inst in the directory. If you are installing TrueType fonts, (remember, not all distributions can use TrueType via xfs), prepare the new directory for the server by typing the following while in the directory containing your new fonts:
ttmkfdir -o fonts.scale
mkfontdir

So I ran those two commands, each of which apparently completed successfully. (At any rate, there was no feedback. The system simply returned me to a prompt). Then I ran chkfontpath -a /usr/share/truetype again, and this time it completed successfully (or appeared to). The instructions go on to say:

If xfs is already installed on your system, you should see which port it is running on. You can do this with the following command:
ps ax | grep xfs.
Then check your XFree86 font path with this command:
xset -q
If your font path includes something like unix:/port_number, where port_number is the port on which the server is running. Then you already have xfs set up properly.

Well, I couldn't do the first part, because the pipe character on my keyboard doesn't work. Apparently I have the wrong keyboard defined or something. But I did use the xset -q command, and it returned a bunch of text which included "unix/:7100". That was close enough to their "unix:/port_number" (note the transposed colon and slash) to make me think everything was set up correctly. I rebooted the system (I know, I shouldn't have to reboot as often as I do, but I'm still using the "when in doubt, reboot" method)". The system booted normally, and I used xset -q again to make sure that the "unix/:7100" was still present. It was, so I expected my fonts to work properly.

I fired up Mozilla and the fonts were as ugly as ever. I figured I might need to reset Mozilla to use another font, so I went to Preferences and found that several (but not all) Microsoft fonts were now showing up. So I selected one for a sans-serif font. I was kind of expecting Mozilla to start using that immediately, but it didn't. Just in case, I exited and restarted Mozilla. Same old ugly fonts.

Obviously, something wasn't right. So I went off in search of more information. I found this page, which makes it clear that I have more work to do to get TrueType fonts working on my Linux box. Alas, I'm out of time for now. I have some stuff to do before I get ready to leave for the wedding. I don't doubt that I'll get this working, but the instructions could be a lot better.



Tuesday, 23 April 2002

9:45 - At this point, I'm just using my Linux box rather than trying to improve it. I'll get back to doing that sometime soon, but right now I have a lot of work to get done, so I'm willing to put up with minor aggravations--the lack of TrueType, no ad-blocker, etc. I continue to be impressed with Linux, but there's no doubt that it's harder to install and upgrade software under Linux than under Windows. For all that people complain about DLL Hell under Windows, it seems to me that Dependency Hell under Linux is at least as bad. Probably worse.

Part of the problem, of course, is that Linux isn't an operating system. It's a kernel, around which many similar operating systems have been built. The similarities are much greater than the differences, but those differences can still bite you.

I've been accumulating Linux-related mail since the end of last week, so it's time to post some of it. The first is a continuation of my exchange with Mark Huth.

From:     Mark Huth
To:       thompson@ttgnet.com
Subject:  RE: Linux vs. windows.
Date:     19 Apr 2002 12:57:31 -0700   

Bob,

I'll respectfully disagree with the linux user ratio.  It has been my experience that the ratio is much closer to 1:1 than you'd suggest.  Indeed, some months ago Jerry opined on his web page that he thought the fonts stink on a Unix box.  (He was more eloquent and more politic).  I was struggling with that very issue and seconded his opinion and asked for help from his readers in making my fonts less ugly.  I was not aware of the font de-uglification how-to at that point.  I was inundated in nasty comments from Linux users, including a horrid exchange from [name removed by RBT] who kindly suggested that I must be a computer dunce because I didn't understand the explanation in the how-to.  I learned two lessons from the experience.  First, don't say anything anti-Linux on a well read web page. Second, don't respond to nasty emails from Linux users.  Many aren't interested in discussion or education.  I did get several comments that were helpful, but the ratio was at least 10:1 nasty:helpful.  Sigh, no real point to this, but I don't get the same kind of response from the AIX users.

I honestly like Linux and the idea of Linux, but I'm very doubtful that the 'tide' of applications and tools available on Windows is going to make it to Linux at any point.  I'll paraphrase one of my friends, who is the CEO of a 6 billion dollar medical software company:  "I really hate Microsoft and hate depending on them, but until we see Linux standardized, and we see professional support and development available, I can't bet my company on it". 

We are only a 6 million dollar/year company, but I can't bet my company on Linux either. 

Sorry to hear that. My own experience has been a lot different. The standardization issue has some validity, but of course one can standardize on one distribution and not worry about the others.

Well, apparently I'm not going to post any more mail. I had a hell of a time getting that previous message copied and pasted from Evolution into Mozilla Composer, and now I'm unable to copy/paste at all. The last batch I did worked easily. I highlighted the message and header in the Evolution preview window, copied it from there, and pasted it here. That no longer works. Nor does opening the message and attempting to copy/paste from there. Perhaps it'll work if I reply to the message and try copy/paste from that screen.

Nope. Same thing. I copy the text, come over to Mozilla Composer, and try to paste it. There's a pause of a couple seconds, and nothing shows up here. This is very frustrating. I need to get some real work done, so that's all for now.



Copyright © 1998, 1999, 2000, 2001, 2002 by Robert Bruce Thompson. All Rights Reserved.