Relevant part:

curl > cpanm
chmod +x cpanm

I find that CentOS and Scientific make email setup fairly easy, at least for the simple configurations I need.   But I ran into a small problem getting Thunderbird to connect to an IMAP account on a different VM.  Ultimately, I found that this was helpful:

The key was setting the mail_location in the dovecot.conf file.

Another chapter in the endless saga of grief with this.   The worst part is that every time I encounter a bout of this inability to print from Windows, it ends up having a different solution.

About a week ago, printing from the Windows laptop suddenly stopped working.  I had not rebooted or meddled with the Linux box that hosts the printer at all; in fact, the host had been up about 60+ days straight without a printing incident arising.  That time, it turned out that restarting the cups server on the Linux box solved the problem.

Today, the printing capability from Vista stopped again, but restarting the cups server did not solve it this time.  There is a difference, though, because this happened after upgrading that same host from Scientific 6.3 to 6.4.

One issue I notice is that I can ping the Windows machine (which has a fixed address now; I forgot I did that some time back, probably to help with just this sort of problem) from the Scientific Linux box.  I opened the ping “port” on the server and tried to hit it from the laptop, but no go.  The laptop can see the wireless router, but nothing else — this has always been an issue, btw.  Worse yet, this router does not have a way of displaying its internal routing table so far as I can tell.  So I don’t know how things are going bad.

My next step may be to try using wireshark to track this down.  But I am wondering if the next Windows reboot might resolve the problem as well.  That laptop may be running since before I upgraded the linux box.


openssl req -x509 -newkey rsa:2048 -keyout key.pem -out cert.pem -days 1000 -nodes

There are no ssh “shares,” of course, but I found this while trying to create a Samba share connection through an ISP.  Turns out, this is much easier, and far more secure.

This page also gives a good summary of creating the ssh keys:

ssh-keygen -t rsa
scp .ssh/ user@server:
ssh user@server
mkdir --mode=0700 -p .ssh
cat >> .ssh/authorized_keys
chmod 0600 .ssh/authorized_keys

Really too easy:

Handy, so why not… has a lot of useful stuff like this.