The Boston Diaries

The ongoing saga of a programmer who doesn't live in Boston, nor does he even like Boston, but yet named his weblog/journal “The Boston Diaries.”

Go figure.

Tuesday, February 29, 2000

Life in Unixland

ytalk doesn't work on linus (my home system). Nor does talk. Strange, I have it enabled, but it just isn't working and it seems to be horribly damaged.

This is Unix. So what else is new?

Seriously. There are at least two different talk protocols, neither one documented (unless you count source code to be usuable documentation, much like uuencode when you get down to it) and both incompatible with each other. Which is why ytalk is nice—it preportedly talks both so it doesn't matter.

Only it's not working.

Over the years I've found it harder and harder to find working implementations of *talk on any system but I did have a working version I could use to talk to a few friends with before the install of RedHat 5.2 on linus (it was running RedHat 5.0 before).

Now it's general braindamage all over the place.

In trying to debug the problem, I found that /etc/inetd.conf had a bogus entry for dtalk (whatever that is) so I commented it out. Still didn't work. Uncomment telnet on the advice of Mark to see if inetd is okay.

telnet isn't working. What the … ? I try killing off inetd and restarting it. Same deal.

Is it possible for a newer release to exhibit so much lossage? That isn't a Microsoft product?

Try re-enabling FTP. Same lossage.

Turns out I had neglected to install TCP-wrappers. Nice that the RedHat install program neglected to make a dependancy on that. But it includes Perl. Goes out of its way to include Perl.

Such is life in Unixland.

I should note that I get easily upset when stuff that should work doesn't. Computers don't have to be this difficult. There shouldn't be this much lossage and braindeath in dealing with computers. But I suspect that most programmers can't cope with such ideas. Programmers give programming a bad name.

Obligatory Picture

[It's the most wonderful time of the year!]

Obligatory Contact Info

Obligatory Feeds

Obligatory Links

Obligatory Miscellaneous

You have my permission to link freely to any entry here. Go ahead, I won't bite. I promise.

The dates are the permanent links to that day's entries (or entry, if there is only one entry). The titles are the permanent links to that entry only. The format for the links are simple: Start with the base link for this site:, then add the date you are interested in, say 2000/08/01, so that would make the final URL:

You can also specify the entire month by leaving off the day portion. You can even select an arbitrary portion of time.

You may also note subtle shading of the links and that's intentional: the “closer” the link is (relative to the page) the “brighter” it appears. It's an experiment in using color shading to denote the distance a link is from here. If you don't notice it, don't worry; it's not all that important.

It is assumed that every brand name, slogan, corporate name, symbol, design element, et cetera mentioned in these pages is a protected and/or trademarked entity, the sole property of its owner(s), and acknowledgement of this status is implied.

Copyright © 1999-2023 by Sean Conner. All Rights Reserved.