[Editor: I haven't installed Tomcat on my machine, but just glancing at the page of instructions linked here shows them to be easy to follow and clearly written. Probably well worth the visit if you want to get Tomcat and Apache working happily in X.]
[Editor: Revised completely to reflect the tips added to the comments - thanks everyone!]
If you have a dynamic IP address (one that changes every time you connect to the net), there are a number of GUI tools that will display it for you. However, if you want to be able to get your IP number from a terminal session, the following appears to be the easiest way. The command uses 'wget' to read the contents of a web page that returns your IP address as seen by the external web server, and then processes the web page to extract the IP. The command to type is:
NOTE: Shown on two lines for a narrower window; enter on one line and replace [space] with an actual "space" character.
You'll get a single line containing your external IP address. Note that this will only continue to work as long as tools.lyceum.net doesn't change the format of their web page! Thanks to everyone (see the comments) who contributed to the development of this tip.
Read the rest of this article for an explanation of how it works, and a way to make an easy to use "alias" that will make it as simple as typing "showmyip" or whatever you'd like to call it.
From the editor: Would you like the ability to easily access web sites you set up by name, instead of by number? If so, you'll want to use Virtual Hosts in Apache which will let you do just that. Read the rest of the article for jaccorens' instructions on how to configure it. I have not done this yet on my machine, but intend to ... someday when I get some free time!
With the release of mail.app and OS X, Apple switched the mac.com email server from POP to IMAP. For most users, the change won't have a dramatic impact. However, there's a key difference between IMAP and POP. With POP, you retrieve your messages from the server, and (unless you tell it otherwise) they're deleted from the server. IMAP basically functions the other way around - when you're looking at your email in mail.app, you're actually looking at the IMAP server (those who know IMAP better than I can probably give a better description of the actual process). mail.app won't download and remove your mac.com mail unless you actually (a) delete it, or (b) move it to another mailbox. This has led some users hitting mac.com disk limits due to a large amount of email kept on the server.
If you'd like a simple method to prevent this from happening, read the rest of the article. This solution was distributed by Ron C. to the X4U mailing list.
I really loved the "Connect To..." alias from macOS 9 and below. Unfortunately, Apple neglected to put something like it in OS X. I decided to take matters into my own hands and created an OS X script that opens any URL as specified in a dialog box from OmniWeb. You can download the working applet, or the source if you wish @ http://homepage.mac.com/the_hoffmans/
email me at email@example.com if you like it!
If you get mail with a picture from somebody sending mail with Eudora and you try to read it in Mail.app you might need to tell them to re-send that picture as an attachment and not embedded between lines of text. If they don´t the only thing you see of that picture is a tiny little purple icon. Me and a friend triple checked this in mail sent with Eudora (5.x) and we also used AppleDouble, AppleSingle, BinHex and Uuencode data fork. So ask them not to paste or drag & drop any pictures between lines of text. They can paste the picture after the last word or as an attachment.
I don´t know if Mail.app is to blame but I know the problem will end up in Apple's Mail.app for MacOS X. The different encodings do not affect the jpeg-picture or the message.
This is really only relevant if you've followed the instructions from StepWise on how to configure and install Apache 1.3.19 and PHP 4.0.4pl1. What I discovered was that when you restart Apache, it will basically hang because of an error related to the apxs binary in /usr/sbin (take a look in the Console app for the exact error).
If you want to run your web server with WebDAV capabilities enabled on it, you will need to download the latest version of mod_dav, configure and install it, replacing the pre-installed module for Apache. The information for installing mod_dav can be found on the mod_dav site, but I will summarize it here.
Read the rest of the article for an excellent how-to on installing WebDAV support onto your new Apache...
I noticed that you talk about how to compile lynx. There is a *much* better text based web browser called "links" it resides at this URL. I downloaded and compiled it without any problem. It handles tables, and frames correctly. It is my browser of choice on OSX... it has yet to crash on me in many many hours of use.