Well, we finally got a TiVo. I had been slightly resisting the notion of getting one, since I think they are expensive and I don't watch enough TV to make it worth the cost. But more than a couple times this past year, Tess and I have caught ourselves saying to one another "You know, if we had a TiVo, we could pause that show..." or "If we had a TiVo then we could have watched Six Feet Under even though we went to Phoenix this weekend..." So I guess having a TiVo is perhaps most helpful if you don't watch a lot of TV. Or you have a busy schedule with which those few shows you like don't coincide. Or something. A TiVo makes a nice gift, especially for those who find themselves waffling on the matter.
One more barrier to entry into the world of Digital Video Recorder ownership was the fact that you need a phone line for it to use. My TV is way over in one corner. I have cable, power, and 3 10/100 CAT5 drops back there. I don't have phone. My house, in fact, has only 2 phone jacks and the one closest to the TV sits on the other side of a sliding glass door. I didn't want to run phone line over the wall, and I can't get into the ceiling. I also don't want any more conduit on the outside of the house if I can help it. They say that you can buy a wireless modem (not, apparently, a wireless phone jack) if you don't have jacks nearby. Anyone who has been in my house knows that I need another wireless device like I need another project on the back burner. I'm running short on plugs in my house to boot.
The only "real" solution would be to crack open the case of the unit, add a NIC, and plug it into my existing 10/100mbps network. That means voiding the warranty (possibly before I even knew if the thing worked or not), ordering the kit over the Net, hooking it all up and hoping. It just looked like too much trouble to go through in order to have the ability to get that show I missed because I was traveling one weekend or had to work late or whatever.
Well, the Series 2 TiVo (the most current one) has USB ports on the back. That opened up some possibilities. I did some investigating. Turns out that the Series 2, it was rumored, has built-in (if "unsupported") support for various USB-to-Ethernet adapters which can plug into these ports. So Tess and I asked for TiVo for Christmas. I figured I could hammer out the networking issues when/if it came (this was last summer at some point) and I collected all the links I'd found into one place for safe keeping.
When it came time to unbox the TiVo yesterday, I had to go get an Ethernet adapter. I didn't know what kind to get. After looking through the links I'd saved, I realized that I'd never looked for a supported products list in my earlier research. (I suppose it never occurred to me, at the time, that one adapter would be supported when one other one wasn't; I also wasn't aware how many chipsets there are for USB Ethernet adapters.) After some time googling, I couldn't find a reliable list of supported adapters. I did find some long-ish lists of product names and such, but none of them had the same information. One list had a certain product, but two others didn't and so forth. I couldn't even pick one to link to, in fact. Figuring that the union of those lists would yield a supported adapter, I went to Fry's and picked up a Linksys USB100TX 10/100 USB Network Adapter.
I set up the TiVo last night. I figured out where it all was going to go, what unit was on top of what other one (we have a big 48" TV and we just put the various components on top of it: an A/V receiver, a DVD player, a cable box, an AudioTron and an Apple AirPort), and I got it all arranged so no one item will cook another. Then I realized that I was about to use up the last of my 3 Ethernet ports on my wall jack (the AirPort and AudioTron taking up the other two). Something about this really bugged me. But I had an idea.
I happened to snag an old 10mpbs hub from my brother Trey when I was at my mom's store over the holidays. A whole box full of aging network gear had come in, and he was going to donate the lot (the kind of people that shop at my mom's store don't buy "antique" computer hardware -- even if she had someone able to test it all to make sure everything worked before it went out on the floor). I rifled through it all and grabbed and clean-looking, rackmountable hub and some new patch cables (one can never have enough cables or wire). I was going to use it for network sniffing and testing and such (since it was a hub and not a switch), but because nothing in/on/around the TV takes up much bandwidth (the AudioTron streams MP3s which are sampled at only 128kbps; the AirPort runs 802.11b, which tops out at 11mbps -- a speed which is still much slower than most of the Internet sites it'll be used to view and not much faster than the top speed of the hub) the answer seemed to be clear: plug everything into the new hub behind the TV. I'd be burning an outlet, but I'd have a nice networking setup. After looking at the hub again, I realized that it had a surface mount kit on it, not the rackmount kit I thought it had. That made the decision all the more clear. I went and grabbed 4 wood screws and a drill and mounted the hub right onto the frame of the window behind the TV.
So I plugged everything in all over the place and turned it on. My previous research told me what I needed to do to get the TiVo to use the USB NIC instead of the phone line: when it came to set up the dialing properties, I told it to use a dialing prefix of ",#401" (no quotes). By the way, that is entered with "Pause Enter 4 0 1". I still gave it my phone number and area code and everything though -- it wouldn't continue without it. But that was all I need do, according to what I had read. (The advice was correct, as it turned out. But I didn't know that last night.)
So before I hit "Select" to have it start to go out and grab its update, I went over to the TV so I could see the lights on the hub and the NIC, with the latter having no link or activity lights at all. There was link on the hub, but nothing on the LEDs on the actual NIC. My heart sank a bit. For a moment I thought it was asking a little too much for someone who has never even used a TiVo to be able to get it set up using an unsupported, hypothetical network system using possibly dodgy parts rather than it's built-in modem and a phone line. I hit select anyway and went looking for the phone cord and phone jack splitter I had bought just in case. I didn't know if I'd like having a phone cord draping over my vertical blinds, but I thought I could maybe just plug it in once a week or something and tell it to update manually or something. What a disgusting, manual solution. The thought made me not want to have a TiVo at all; if it couldn't do Ethernet then it was of no use to me.
While I was getting the phone cord, it had apparently made some progress. The on-screen message said that the initial setup would take 10-20 minutes, but I had only been turned around for maybe 90 seconds. No network activity was present, but it was clearly doing something. Did the fact that it did whatever it had to do really quickly mean that it got out and grabbed the data over my fast cable modem link and didn't need to take the 20 minutes a phone line would need, or did it mean that it couldn't do anything at all network-wise and had decided to punt? There was no way to know, so I kept moving forward under the assumption that magic TiVo bits were very stealthy and didn't tickle NIC or hub LEDs. After it did it's initial processing, it said that it had to go out and grab actual programming information, so it could tell us what channel were what and so forth (meanwhile I'm still wondering if maybe it couldn't get out on the Net and decided to use some fallback setup config instead). It said I shouldn't use the phone for the next 45 minutes to an hour, and that it would take around 8 hours to process information thereafter. So I decided to keep one eye on the on-screen progress info and the other eye on the hub's lights while it did it's network thing.
After watching a while I still couldn't see anything on the adapter's LEDs, but after a bit the hub lit up like a Christmas tree. Maybe the USB adapter's LEDs need software support that the Linux-based TiVo wasn't giving it? Who cares. Success was at hand. We had achieved operational TiVo satisfaction as the unit was, in fact, getting on the Net sans modem or phone line. And it was doing a really good job of getting on the Net as well. I starting poking around in the system information menus and saw an entry for "System Status" or "Current System Activity" or something like that. After maybe 30 minutes of it doing it's thing, it was 41% done. Figuring that what should have taken like 3? hours took only about half an hour, the whole process should have been done in 75 minutes or so (unless it had to do internal processing on the data it was grabbing, like decompressing gzipped files, building databases/indexes, etc.). I was going to figure out what the theoretical transfer rate was but I decided to get a beer instead (math and beer usually being mutually exclusive for me; if you're curious: figure a maximum estimated transfer of 40kbps for an analog modem, divide by "about 8 hours" and compare the actual time it took to move the file(s) to my TiVo -- which I didn't finish timing due to the beer, but which was "about an hour and change").
So we're essentially all set up. I'm not quite sure if I like the TiVo's menu or not. I told myself that any new interface takes getting used to. I also have to fix it up so that the TiVo remote can work the TV volume and whatnot, but that's easy. I can't wait to record Good Eats (of which I've seen perhaps half of the available episodes, even though I actively and consciously try to make time to watch it on the weekends), Conquest and Mail Call.
The only thing bugging me is that my A/V receiver now has a supremely annoying hum in it (it actually always had a bit of a hiss, but only when it was turned way up and was on the AudioTron input). It's a plain old 60 Hertz hum, but it happens when I listen to the AudioTron input, the DVD input, etc. And it's "sub-cyclical" as well: there's a "pulsing" to the hiss with about a one second period. This is with the TV's volume on mute. The only thing different is that I now have a TiVo plugged in to the same 120V leg as the receiver. I'm going to shut the TiVo off and pop in a DVD and see if it's still there. If anyone with more of an electronics clue than me (about 80% of the US population, probably) has any ideas, I'd love to hear any advice you have to offer...
You can't use CPAN to install the DBD::Sybase Perl drivers on Linux. There are a couple things that need to be tweaked by hand.
1. Download FreeTDS from http://www.freetds.org/. This a free alternative to Sybase's ct-lib library packages (which I couldn't find anywhere on their web or ftp sites, and which I wasn't willing to install the whole DB just to get).
2. Build FreeTDS: './configure --prefix=/usr/local/freetds; make; make install'.
3. Open /usr/local/freetds/etc/freetds.conf and add a section for the server you're using. An example:
? ? ? # This is an example Sybase server
? ? ? [SYBASE_EXAMPLE]
? ? ? ? ? host = sybase.example.com
? ? ? ? ? ;host = 192.168.1.125
? ? ? ? ? port = 2025
? ? ? ? ? tds version = 5.0
? ?You'll use the string 'SYBASE_EXAMPLE' in your perl scripts as the server to connect to, like so:
? ? ? my $dbh = DBI->connect("DBI:Sybase:server=SYBASE_EXAMPLE",'user','pass');
4. Download the DBD::Sybase tarball from http://search.cpan.org/CPAN/authors/id/M/ME/MEWP/DBD-Sybase-0.95.tar.gz. (The online docs are at http://search.cpan.org/author/MEWP/DBD-Sybase-0.95/Sybase.pm.)
5. Edit DBD::Sybase's dbdimp.c (it's in the top of the untarred directory), and change every cs_ctx_global() you find to cs_ctx_alloc(). There are probably four occurences to change, so do a global search and replace.
6. Edit DBD::Sybase's CONFIG file (it's also right on top there). Add the following lines:
? ? ? SYBASE=/usr/local/freetds
? ? ? EXTRA_LIBS=-linsck
7. Do the standard 'perl Makefile.PL; make; make install'.
8. Run a test script to make sure it all works.
It's another update-a-copia.
I found a good list of well-known ports used by trojans and worms. It's got SubSeven, Slapper, BackOrifice and about everything else you can think of.
On an unrelated note, I also came across a utility called ettercap.
Ettercap is "a multipurpose sniffer/interceptor/logger for switched LAN. It supports active and passive dissection of many protocols (even ciphered ones) and includes many features for network and host analysis". It'll sniff passwords out of lots of common protocols, drop certain packets, re-insert certain packets, and allow one to cause general mayhem. I'm going to install it one day soon and see what I can see. I wish I could use like my neighbor's cable connection, though; I'd like to see what he could possibly see.
Pardon my french, but the USPTO is staffed by a bunch of braindead morons. This ought to be against the law. Awarding patents like this ought to mean that the patent examiner who approved it is personally liable for making things right when the patents are found to be nonsensically awarded. It ought to mean that (s)he get's horsewhipped when someone can tell them "Do you know what 'IRC' stands for? Ever used CompuServe or a BBS? Have you ever used 'talk'? Asshole?"
It just boggles the mind how much arbitrary wealth the low-bid, non-technical rubber-stampers at the USPTO wield. It's very scary.
I'm nearly totally positive that I have created the very first Mary Lou Retton online gymnast clock. I'm, like, 99.999% sure that I made the first and only one. Me.
Although it's odd... I can't stand Mary Lou Retton. Never could. That squeaky little bitch annoyed me to no end with that smug grin of hers. Put me off Wheaties for life. Even her name "Mary Lou" bugged me. I mean, pick one goddam name and use that one, already! Jeez! I'd even prefer Spuds MacKenzie over Mary Lou if I had to pick. But I think she's just funny as all get out as an online clock. I dunno how to explain it, but I find myself cracking up uncontrollably every time I check the time. Maybe I need to start taking vitamins.
This was mercilessly stolen from a Slashdot post I saw recently. I thought it was another "funny things about Star Wars" repost/spam email thing I'd surely seen, but I'd never heard it.
I had to wipe my monitor off after reading some of them. To think I went 25 years living and breathing everything Star Wars and I never thought to slip the word "pants" in there every once in a while. I'm not nearly as clever as I thought I was. Anyway, I present:
25 Lines From Star Wars that can be improved if you substitute the word "Pants"
I was having a chat with someone about the Roman/pagan origins of Christmas. I happened across a good page on the History Channel's web site that explains it pretty well.
Happy shopping!
This is taking things too far. This guy overclocked his Christmas tree lights. Some people just can't leave well enough alone.
If I had any musical talent at all, I would want to play guitar. I would want to play guitar like Johnny Ramone. I think that's shooting low, yes, but for some reason it's damn infectious music (although that could be my Asperger's talking). The barrier to entry is certainly low, with satisfiying results achieved after minimal effort.
I'm all over it.
I was playing with OpenSSL at work today. Turns out that you can encipher stuff right from the command line. It's pretty cool.
To encrypt something, do this:
? ? /usr/bin/openssl bf-cfb -salt -a
Then you enter the password twice, then the text you want to encrypt, then ctrl+d to finish. You should see some encrypted text. To decrypt that text run this:
? ? /usr/bin/openssl bf-cfb -d -a
Then it'll ask you for the password and then the ciphertext. Hit enter and then ctrl+d when done. You should see plain text.
You could use this as a hinky messaging system. All you'd need is a one-time pad scheme to figure up the password and you'd be able to send ciphertext via email or IM securely. Of course, you could use a GPG or SSL-aware client, but not all of them are (GAIM isn't, for example).
I got this email this morning at work. This is one of the funniest things I've read in a while. (BTW, AP&M is the computer science building at UCSD). I think they should give that art student free financial aid or something.
Date: Thu, 12 Dec 2002 07:13:02 -0800
From: Wayne Frater <>
To: , , ,
, , ,
Subject: Signs on water fountains
All APM,
I called EH&S re: the 'posted notices'. Here is their response. I,
and they, are also talking to Vis Arts to determine if this was a
'finals project' and to express our opinions about stepping over the
line.
Wayne
EH&S Response:
As some of you may have noticed, a number of signs have been posted
over campus drinking fountains warning that the water has been tested
and contains "dihydrogen monoxide". The sign goes on to list all of
the dire health consequences of consumption (bladder discomfort,
etc.) and at the bottom of the sign is a UCSD logo and the words
"UCSD Environmental Health and Safety". A sample is on the door to
my office.
Of course "dihydrogen monoxide" is just water. The signs appear to
be the work of a rogue visual arts student, but several people around
campus didn't get the joke and were very alarmed. Signs have been
removed from the VA building and AP&M, if anyone sees any more
around, please remove them.
The most significant issue is that the logo and our office were used
to give the signs a semi-official appearance. I am trying to reach
the professor for the VA class that most likely produced the signs to
discuss this and other issues. In the meantime, if anyone gets any
calls, please reassure people that normal safety precautions are more
than adequate for handling this material - Jim
Jim Kapin
Chemical Safety Officer, UC San Diego
nnn-nnn-nnnn, fax nnn-nnn-nnnn
9500 Gilman Drive, MC 0920
La Jolla, CA 92093-0920
mailto:
--
Wayne K. Frater Academic Computing Services Univ. of Calif @ San Diego
I was getting gas after work today at the overpriced station on La Jolla Village drive and I noticed something weird: a wallet laying on top of the gas pump. It was just sitting there, open and everything with the credit cards and driver's license showing. It was like one of those hidden camera shows where they leave a $100 bill on the sidewalk and film what people do when they find it. I looked around and couldn't see a camera. I wound up just staring at it while I stood there filling up.
I ended up looking inside it. The guy's license said his name was Carlos. He had a couple credit cards, a debit card, a UCSD student ID and $64 in cash. When I got done filling the tank, I grabbed the wallet and headed towards the cashier office/minimart thing to turn it in. The clerk was a liitle taken aback when I gave it to him. He opened it up first thing when I handed it over and got this incredulous look on his face when he saw cash still inside. He looked at me like I was wearing a dress or something. I contemplated making a note of Carlos' address so I could let him know how much cash and cards were in it when I turned it in, but I didn't.
I still don't know how someone could leave their wallet at a gas station. You take a wallet out, pay, and then put it back. That's how it goes; that's habit. I should have checked to see if Carlos was shorter than 5' 10", which is about how high the tops of the pumps are. Maybe Carlos set the thing up there while he filled up and forgot it because he couldn't see it up there.
Anyway, I did the right thing and hopefully Carlos won't be out any money. More karma points in the bank. If I ever forget my wallet somewhere, I'm expecting it back in one piece, with its contents intact.
In case anyone is wondering what to get me for Christmas, I can think of one thing I wouldn't mind having...
For some reason , I got a bug up my butt today about the haiku error messages from BeOS. When an app encountered an error, the user would get a little poem about it. For example, if you tried to get a web site that didn't exist, the web client (which was called NetPositive) would say something like:
? ? ? ? ? ? Ephemeral page
? ? ? ? ? ? I am the Blue Screen of Death.
? ? ? ? ? ? No one hears your screams.
There were a whole bunch of them, throughout the OS. I remembered installing BeOS 5 Personal Edition years ago and then just hitting reload on a non-existent URL like an idiot for like 30 minutes trying to see all the haiku. It was a small thing, but I thought it was a brilliant, elegant touch and typical of the entire operating system. It was inspired.
I decided that the BeOS haiku would make smashing 404 messages for this site as well.
I posted to Slashdot about software SDSC wrote called "Secure Syslog" which replaces the regular syslog daemon. It's released under UC's standard "free for non-commercial use". Well, I had never seen any official policy on what the license is all about. I went and dug around for like 20 minutes and finally found the UC guidelines for releasing software.
Basically, anything I write can be given away in source form, as long as I follow the policies, include the UC license with it, and stipulate that it's for non-commercial use. I think that's execptionally cool. Anything the CSE department comes up with can be given away free, source and all. Try that at patent-happy Qualcomm.
The pictures from our London trip are online. We have pictures from four different days:
- 11-25-02
- 11-27-02
- 11-28-02
- 11-30-02
Note that the pictures might not have all been taken on those days. The dates are merely when we dumped the images form our camera to the laptop. Well, we usually copied pics at night, so all the events happened on or before the date on the web pages.
Also, you might notice George and Perky the travel bug in quite a few pics. They had many adventures around London and are going to get their own page real soon, so stay tuned.