February 2004 Archives
I haven't heard of this idea before in this exact form.
Background: the other day, Red Hat released Fedora Core 2 test 1 (the hobbyist version of Red Hat Linux), so in the height of optimism I tried downloading all 2GB of it over my DSL line at home. I normally get 26 KBps, but this time I used BitTorrent, and because so many people were simultaneously downloading it, I averaged about 100 KBps and completed the download easily overnight. I have _never_ had such high download rates over my DSL line.
Then this morning the FCC shut off Howard Stern, and there are talks in Congress of a 10X increase in fines for showing "indecency" on TV, and they want to require a digital delay on all live broadcasts. I don't like Howard Stern myself, but I don't like where this is going. Puritans can go believe whatever they want, but when they use Janet Jackson's revealing costume as a pretext for imposing blanket censorship rules on publicly-owned bandwidth, I get mad, and I want to take the government out of the equation.
To do a case-sensitive search in Emacs, type M-c while in the incremental search box. Emacs also guesses that you wanted a case-sensitive search if your search term contains at least one capital letter.
Over the past couple of weeks I've been getting OpenSSL to build on Windows, and I've been writing test programs to explore the API. I have also removed all the custom encryption code in WINW, which is a good thing. I like the BIO abstraction in OpenSSL; it's similar to what I was trying to do in WINW, but it's better. The similarities have also made it pretty easy to integrate WINW and OpenSSL.
ps axwww | grep httpd | awk '{print $1}' | xargs -n1 kill -9
A "file" consists of the blocks of data in a file, and metadata describing the file (such as the filename).
Using this terminology, a hard link points to the data, and a soft link (also called a symlink or symbolic link) points to the file. Every file has at least one hard link, but not every soft link points to a file.
This explains why the Unix command for deleting a file is called "unlink." When you unlink a file, what you're really doing is removing a hard link to the file data, and when the last hard link to that file data is removed, the system removes the data, too (well, it doesn't delete the data, but it marks it as free).
The Unix command script captures a terminal session to a file. It's useful when documenting how you did something in a shell.
Emily and I wanted to give Mary a little bit of peace and quiet this weekend, so we left her at home and went to Google for a few hours. Here's a picture of her next to a Google Search Applicance:
Emily is trying very hard to stand on her own, and for a few seconds at a time, she succeeds! She pushes herself up, using something nearby as a prop, and then lets go. I've seen her try this over ten times in a row. She's very determined!
This allows you to skip the Linux step.
- Download the OpenSSL tarball and extract it.
- Find the file util\mk1mf.pl.
- Find the line
($key,$val)=/^([^=]+)=(.*)/;and add this line after it:$val =~ s/\s+$//;(this is at line 487 in OpenSSL 0.9.7c) - Now follow the instructions that came with the tarball.
The problem is that mk1mf.pl parses the generated MINFO file into key-value pairs, but in the process picks up the end-of-line character at the end of each value. I bet this is a problem only if you install Cygwin Perl with DOS line endings, which I did (though I tried converting MINFO to Unix linefeeds and it still didn't work).
I know how to build OpenSSL on Visual Studio .NET!!! So can you.
Ingredients:
One Windows machine with VS.NET (my version is 2002, a.k.a. 7.0)
One Linux machine (mine is Fedora Core 1)
One tarball of OpenSSL 0.9.7c.
