FontPath "/usr/X11R6/lib/X11/fonts/misc:unscaled"
FontPath "/usr/X11R6/lib/X11/fonts/75dpi:unscaled"
FontPath "/usr/X11R6/lib/X11/fonts/100dpi:unscaled"
FontPath "/usr/X11R6/lib/X11/fonts/URW"
Get these fonts at GIMP's site, http://ftp.gimp.org/fonts.html. According to that web page, these are the same fonts that are distributed with Ghostscript, so you probably already have these fonts.
There are two Truetype font servers available, each of which is reasonably simple to install -- xfsft and xfstt. xfstt is a server that runs on top of X. It's supposed to be easier to install and get going but is also supposed to have some small incompatibilities (I haven't met anyone who has made an issue of the incompatibilities). xfsft is supposed to be more like a patch to X and is `in tune' with the X philosophy, but is supposed to be harder to install.
You'll find them both at: ftp://metalab.unc.edu/pub/Linux/X11/fonts
You can get xfstt from:
ftp://rpmfind.net/linux/contrib/libc6/i386/xfstt-0.9.10-1.i386.rpm
You can get xfsft from: http://www.dcs.ed.ac.uk/home/jec/programs/xfsft/
You can get xfstt from ftp://sunsite.unc.edu/pub/Linux/X11/fonts/
After installing one of these servers, you'll need some TT fonts. The xfstt FAQ contains many, many links to websites that allow TT font downloads. In fact, if you search Yahoo or dejanews.com, you'll find hundreds of TT fonts on the web; maybe even thousands. Another place to look is at Satan's web site: http://www.microsoft.com/typography/fontpack/default.htm. They're free for personal use, but may not be redistributed. The Windows 3.1 files are self-extracting PKZIP files with .exe extensions. The Linux version of InfoZip's unzip can handle them fine. You can't extract the win95 version of these font packages.
Of course you have friends with Windows. All the fonts are located in a centralized directory; you can simply copy them from their computer to yours via floppy, removable media, network connection or whatever.
I'm running RedHat 5.2 (2.0.36) and the glibc version of Netscape 4.5. Once I open Messenger (I can open then close it), mailto: links work. Otherwise, I get the same problem.I assume the Messenger component initializes something. I found it so annoying that I've configured Netscape to start up Messenger by default (under Edit -> Preferences -> Appearance).
# fetchmailrc written by Peter Jay Salzman Feb 1999
# Comments begin with pound. On the poll line the words and,with,has,wants
# and options are ignored as are :; and , for the rc to resemble English.
# protocol can be abbreviated as proto.
poll landau.ucdavis.edu with protocol POP3
user YY
pass XX
fetchall
# fetchmailrc written by Peter Jay Salzman Feb 1999
poll mail.server.edu with protocol POP3
user bill_gates with pass password is the_devil here
user jack_tripper with pass ThreeCompany is jack_tripper here
user daffyduck with password SuCcutash is root here
fetchall
send-hook 'SABMAG@MITVMA.MIT.EDU' "set pgp_autosign=no"and every message you send to sabmag will NOT automagically be signed. Note that if you simply put
set pgp_autosign=nothen none of your emails will be signed unless you want them to be signed (default is to hit "p" before you send the message).
Here's an example of a signature daemon (written in perl) that basically does what you want. There may be some minor bugs in it that need to be ironed out, but it should give you the general idea.
#!/usr/bin/perl
use strict;
my $NAMED_PIPE = "signature_file";
my $SIG_DB = "sigs.txt";
my $SIG_DELIM = "<<SIG>>"; ### Delimiter in sig database
my @allsigs; ### List of all signatures
my @cursig; ### Lines of signature being read from DB
### Make sure the named pipe exists. If not, set it up.
unless (-p $NAMED_PIPE) {
system("rm $NAMED_PIPE") if -e $NAMED_PIPE;
if (system("mkfifo $NAMED_PIPE")) {
die "Couldn't make named pipe ($NAMED_PIPE)\n";
}
}
### Read in possible signatures.
open(SIGDB,$SIG_DB) || die "Can't open signature database: $!\n";
while(my $line = <SIGDB>) {
if ($line =~ /$SIG_DELIM/) {
push(@allsigs,join("",@cursig));
@cursig = ();
next;
}
push(@cursig, $line);
}
push(@allsigs,join("",@cursig));
### Loop forever
while(1) {
open(SIG,">signature_file") || die "Can't write to named pipe.\n";
### Pick a signature file somehow...
my $sig = $allsigs[rand(scalar(@allsigs))];
### Send it to the named pipe
print SIG $sig;
### Close the named pipe (the current program will think it has read the
### entire file.
close(SIG);
### Prevent the next pipe we open from catching the end of the current
### request.
sleep 1;
}
fortune ~/data/mysigsAlso, in my .muttrc add this line:
set signature=~/.muttsig|The fortune program can be used to create your own fortune database of sigs (takes a bit of work, but not too hard). You can write a shell program or perl program that generates the sig.
Identd should not be used as a method of authentication; anyone with root access can alter their identd response. On many systems (such as FreeBSD and Windows) even a non-privledged user can specify whatever identd response they want. The protocol is most useful on multiuser systems as a method of tracking down problem users. If one of your users is causing problems on another system, that system's admin can inform you of the username of the specific user causing problems, saving you a lot of legwork.
Since the client assumes the identd daemon is trustworthy, it is inappropriate as a security protocol, but it sometimes is used as one. (E.g. SOCKS firewall proxies may require satisfactory ident response to allow connections. Since Windows 9x machines don't support it (no concept of user), most SOCKS firewall configurations don't require it anymore.) The RFC suggests it is useful for auditing.... I think that is optimistic.
Example:
Pete Salzman, having logged in as psalzman on his home linux box, proceeds to use his web browser to point at
www.snoop.com
www.snoop.com is a paranoid company and wants to know the username of whoever just accessed their webpage. They query port 113 on Pete's box (identd's port), providing it with the source port Pete connected with.
Identd looks up the username associated with that source port, and says "psalzman" to caller, and exits.
Should you run identd? That's really a judgement call. On systems with many users, the benefits could be great, but it doesn't serve any particular purpose on a single user box. Not running identd may limit your ability to connect to certain servers - many IRC and some FTP servers don't allow, or severly restrict, non-identd'd connections, for example. However, running it means leaving a service open to the outside world, with all the security risks that entails.
Another thing to consider is that identd can allow attackers to find out valuable information about your system, such as whether a certain service is running as root, the operating system you are running, and the usernames of your users. Consider running identd with the -n flag, which sends userid numbers instead of usernames.
Please report bugs, problems or broken links to me.