13 August 2006 1 Comment

SES San Jose 2006

As usual I start blogging and trickle off into not doing anything with it for months.

Anyway, I had a fantastic time in San Jose at SES. Finally met Dave Naylor and Shawn Hogan, and got to hang out with the usual cast. Six years ago I was at LinuxWorld 2000. The ironic thing is that, SES felt just like LWCE 6 years ago. People are excited about what they’re doing, and it doesn’t hurt that theres barrels of money flowing into the industry.

Looking foward to Vegas, Baby.

14 April 2006 Comments Off

The Mac is Back (with a Vengeance)

I grew up on Macs. From the Mac Plus, to the SE, to an LCIII (in color!!!) then a Performa 6220CD, and a B&W G3 350. I was always a Mac guy, but some time around the B&W the world of Linux lured me over. For about 7 years the Mac was only a secondary machine, while all my attention was on Linux on a PC. I’m happy to say:

The Mac is Back. Along with a slight upgrade.

Before:

Before

After:

After

Theres no ifs ands or buts. This thing SMOKES.

G5

25 February 2006 1 Comment

A New and Different SEO/M Content?

Shoemoney’s posted in his blog that he’s going to be launching a new and different SEO/SEM contest.  I think if anyone can pull this off, its Shoe.  Looking forward to seeing how this pans out…

21 February 2006 Comments Off

Fixing Tor + Privoxy on Debian

A few weeks ago I noticed that some scripts I was playing with weren’t actually using tor even though I was proxy’ing through privoxy. Turns out that when you apt-get install tor/privoxy (at least on stable, ok) it doesn’t actually enable tor via privoxy. The fix is a simple addition to:

/etc/privoxy/config:

forward-socks4a / localhost:9050 .
16 February 2006 Comments Off

We’re Out of Oil. Start Pedaling.

This guy’s web site was linked on Slashdot with the summary that world oil production has peaked, and it can only decrease from here on out. Now, I don’t have a PhD. In fact, apparently that seems to be to my advantage. I don’t need to have a PhD to know that his assumptions are inaccurate. To make his prediction, you need to know the total volume of oil that can be extracted from the Earth. Plain and simple, no one knows this. There are oil fields that are only beginning to be accessible, much less pumpable at this point. Pumping efficiency has also made great strides since the ’60s and ’70s but still has a long way to go. Anyone who claims to know, with any certainty, how much oil is available for extraction from the Earth is lying. Even if he was right, he’s not doing anything useful. Oil, as a major fuel source, will be abandoned long before it runs out. His prediction is that in 2025 we’ll be back to the stone age. I say by 2012 we won’t even remember when oil was expensive. The deman will be so low it will be insignifcant. Huge strides are being made in efficiency, fuel economy, and alternative fuels. Oils days are numbered.

Now where’s my PhD?

6 February 2006 Comments Off

GoDaddy Getting More Questionable

The first big rumbling I heard about GoDaddy was this. It was definitely unsettling, but seemingly an isolated incident. Now it seems even Shoemoney is questioning GoDaddy. This is sketchy territory, and as I collect more and more domains with GoDaddy I have to wonder if now isn’t the time to bail. What I’d like to know is if this stuff is intentional, ie: company policies, or if its just foolish employees doing stupid things. I’ll definitely keep an eye on GoDaddy.

5 February 2006 Comments Off

Tivo, HDTV, PTVUpgrade

I got setup for HDTV just before the big game. Honestly it was coincidence, but it worked out nicely. I’ve had an LCD HDTV for a while, and a projector capable of HD for a long time. DirecTV made me a good offer, and I went for it. So far…

The HD-Tivo is great. I already miss the MRV feature that we’re able to add to the other DTivos, but I can get by. PTVupgrade came through as always with the excellent PTVnet software. Within hours of the DTV installer leaving I had 200 gigs more storage, and full network to my Tivo. I can’t stress enough how awesome PTVupgrade is.

HD is amazing. Find a home theater buff and ask to check out HD. Stores don’t do it justice. You will be absolutely blown away by the difference between SD and HD. Yes, it’s still TV, but it looks amazing. Not to mention some of the HD content (Discovery HD Theater) is amazing. Cuban, I worship you man, but sometimes it seems like HDNet content is just HD for the sake of being HD. No one in their right mind would watch it if it wasn’t in amazing HD.

I finally built a DIY screen for my projector with some info I collected on AVS Forum. More info on that to come, but so far its something I should have done a long time ago.

OTA (over-the-air) HD is so ridiculous. The amount of time people spend trying to tweak their antenna amuses me. That said, it seems like its worth some time investment.

30 September 2005 Comments Off

Homebrewing Beer



Homebrewing Beer
Last updated: 9.30.05 3:00 PM

David Dellanave – ddn – http://www.dellanave.com/projects/

Update: The beer turned out excellent. It takes like a slightly less sweet, and more hoppy Newcastle. We’re going to tweak to get it closer to Newcastle. Check back for more adventures in homebrewing.

I’ve had a bug up my ass to start brewing beer for a long time, and stopping at Northern Brewer for a CO2 refill was the catalyst I needed. I picked up a catalog and looked at it every day for a week. Then I bought all the equipment, and here we are.

The First Batch

This is my (our, my roommate Adam and I) first attempt, obviously. We’re doing a Nut Brown Ale as both of us peg Newcastle as our favorite beer. It’s a “dark” beer, but its light enough that most people who don’t like dark beer even enjoy it. The chocolatey tones of Newcastle are excellent, and hopefully we will get some of that action. Yes we look like tools in these pictures, we tried for that effect. When we run a brewery we’ll be laughing at you, don’t worry.

Making Wort

I’m not going to go through all the steps as I’m not an expert anyway. I’ve read John Palmer’s How to Brew and read all of Northern Brewer’s documentation. The only guide I plan to do is how to fit a Corny keg that shouldn’t fit in a dorm fridge, into one. So, here are the pictures with a brief description:

Steeping the grains… Looking like a tool.. That didn’t take long to get like that

Malt Extract

So the water boiled, we take it off the burner and add the malt extract which is what the happy little yeast will eat up to ferment. Before you become an expert brewer and learn to extract fermentable sugars from grain, you use a syrupy-extract instead. It saves a lot of time and there is less room for error. Honestly, I will do all-grain brewing at some point, but I think this method will stick around for a while with me.

Adding malt extract.. Looking like tools.. More toolish behavior

Adding Hops

Hops give the beer flavor and aroma, as well as acting as a natural preservative.

Adding the first (Challenger) hops.. Hops hops The hops before falling back (I’m blowing on it trying to get the steam down)

Chilling Wort

We hauled the wort to the shower to get iced and cooled with cold water. You need to get it down to about 70F for the yeast. This was not cool at all (no pun intended) and I plan to invest in a counterflow chiller. I also lost my worthy assistant when it was just about ready, so I had to pitch the yeast and pour the wort into the carboy myself. You’ll notice the jump in pictures.

Moving 3 gallons of hot wort.. On the bed of ice This took way too long..

Fermenting

There’s nothing left for me to do now. Lets hope the yeast take to life.

69deg Farenheit

Please start bubbling

17 August 2005 Comments Off

6.2 Slice Upgrade Guide

6.2 Slice Upgrade Guide
Last updated: 8.17.05 12:00 PM
David Dellanave – ddn – projectsdavid

In standard form, this guide is a composition of information from DDB. The Only Druid has posted a lengthy description of everything you would want to know about 6.2. However, despite cries to the contrary, it seems that a step-by-step guide remains useful. If you start to notice how similiar this is to the 4.x Installation Guide you are probably starting to actually learn what is going on as opposed to just typing commands. As usual, thanks are in order to the people who figure this stuff out to begin with. If only they were a little friendlier. AlphaWolf, rc3105, adh and others deserve thanks. Of course, I’d like to improve this guide, so any SPECIFIC suggestions are welcome. – ddn

Warning

As much as a step-by-step guide makes things both easier to understand and accomplish, you are still dipping into the realm of the unknown. For most people, TiVo hacking is a hobby as time consuming as any other hobby. Realize that what you are doing to your TiVo was probably not intended to be done. You may break it, you may lose your recordings (even if you’re not supposed to) and you may piss off your family. For an extra challenge, I recommend starting this process an hour before your teenage daughter wants to watch The O.C. This should only take about half an hour, leaving you with plenty of time. Or not. Keep in mind, other people love the TiVo as much as you do, and if you break it they will be pissed. The information presented here is a distillation of information, and all risks assumed are your own. – ddn

Assumptions

# This guide serves people who wish to upgrade to 6.2 via slices (retaining all settings and shows) from 3.1.1 or 4.0.1 to 6.2. At this point, there are no instructions here to intially hack your TiVo to gain network access to this upgrade. For now, thats an exercise for the reader. If you’re at 4.0.1, you already have network access, if you’re at 3.1.1e I suggest PTVnet to get network access.

# This guide assumes you have a working knowledge of unix and linux. While I believe the steps here are fool-proof, it doesn’t always seem to be the case. This is not a tutorial, and I will not answer basic Unix questions. I did this in one day with tremendous previous Linux experience, and ZERO Tivo hacking experience.

If you have no Linux/Unix experience, you will become frustrated if things don’t work exactly as they should. I suggest a beginner tutorial in Linux. It should get you started on the basic commands.

### You will need a USB Ethernet adapter to complete this and use all your new features. A serial cable is not necessary to complete this guide. However, if it doesn’t work a serial cable is mandatory for figuring out whats wrong. Get yourself over to 9th tee and get a TiVo Null Modem Serial Cable. Or make yourself one. Go get yourself a USB200M or USB10TX or similar.

#### I applied this to my SD-DVR40. This guide applies to both RID and Non-RID TiVos. Unlike the 4.x guide, RID is not an issue here. Carry on.

##### This guide uses LBA48 kernels etc. Technically you only need to do this if you plan to use disks larger than 137GB. However, I know of no reason that using LBA48 with smaller disks would cause a problem, so there is no reason not to.

*** Hard to read?   Click here for fancy stuff around the commands.

1: Download the following files into a directory. Unzip zips, and unrar rars. Leave .tar’s intact.


62 init_framework_ddn.tgz
Download Local
This is a simple init_framework including the kernel AlphaWolf posted in his init. Hopefully you don’t mind.
superpatch-67all-NutKase-1.0.tcl
set_mrv_name_67.tcl
Download here

tivotools.tar (extract it from the .rar file)

Download here
Only needed if using PTVnet to initially hack the TiVo (or tivotools wasn’t installed)
Clicking these links and downloading the attachments is not a substitute for reading EACH of the threads they were posted in. You will gain a tremendous amount of knowledge of each utility, and answer any questions you might have.

2. Download a set of 6.2 slices. I would really like to host these locally, and since 6.2 is germane on DTivo hopefully I can. For now:


62_dtivo_slices.zip:
ed2k://|file|62_dtivo_slices.zip|54621252|0C19FAA0C99F4724A412EF546FAA71C0|/

BitTorrent

3. The 6.2 slices you’ve download contain an error in them, so we’ll unpack them, fix it, and just package up the ones you need.


3a) Unzip the 62_dtivo_slices.zip file.
3b) Take a look at the index.txt file (Notepad won’t display the Unix line endings correctly, use Wordpad or Metapad). Your TiVo service number should start with 3 digits. Yup, look on the back of the TiVo. On my SD-DVR80, it is 321. In the file you’ll see the slices for each service number. For example, my DVR80 needs 6.2-01-2-321. The string “6.2-01-2-321” is important, write it down or remember it. So I want these files:

6.2-01-2-321/GZcore-44090111-2.slice.gz

6.2-01-2-321/GZkernel-44090113-2.slice.gz
6.2-01-2-321/swsystem-44090120-2.slice.gz
6.2-01-2-321/utils-44090115-2.slice.gz

3c) Figure out which ones you need, and un-gzip each one of them. Then un-gzip loopset-dtv-Series2.slice.gz, and THEN do it AGAIN to the same file. On Linux you need to rename the file to .gz again otherwise it won’t recognize it as a gzip file. This could all be done quite easily on the TiVo, but now with those 5 files you have a nice package you don’t have to mess with again.

4. Upload the 5 6.2 slices to the TiVo into /var/packages/. Since I use Linux as my main system, I usually tar these 5 files up into a tarball, and just upload that. Also upload the tivotools AIO toolset if you TiVo doesn’t have it or lacks the dbload command.


ftp 192.168.3.105 # FTP to the IP of the tivo

cd /var/packages/
put GZcore-44090111-2.slice
put GZkernel-44090113-2.slice
put swsystem-44090120-2.slice
put utils-44090115-2.slice
put loopset-dtv-Series2.slice
put tivotools.tar

4. Telnet into the TiVo and execute this command to load the slices into the database:


mount -o remount,rw / # Get this out of the way, although not needed until later

mkdir /tivo-bin/ # If you don't have tivotools
cd /tivo-bin # If you don't have tivotools
mv /var/packages/tivotools.tar ./ # If you don't have tivotools
tar -xvf tivotools.tar # If you don't have tivotools

cd /var/packages
/tivo-bin/dbload *.slice
# You might have your toolset in /busybox instead of /tivo-bin.

5. Two modifications must be made to the installSw.itcl script. One is to remove the reboot command, the other is to add an extra argument ($name) to the updateroot command call. If this is nonsense to you, well, thats fine.


vi /tvbin/installSw.itcl # a vi quickstart guide

Original:
file mkdir /var/utils
exec $env(TIVO_ROOT)/tvbin/jpm -p $fil
putlog "Executing updateroot /dev/hda /install /var/packages"
exec /var/utils/updateroot /dev/hda /install /var/packages >&@ stdout

$swsys setActive
# Clean up

Edited:
file mkdir /var/utils
exec $env(TIVO_ROOT)/tvbin/jpm -p $fil

putlog "Executing updateroot /dev/hda /install /var/packages $name"
exec /var/utils/updateroot /dev/hda /install /var/packages $name >&@ stdout

$swsys setActive
# Clean up

Original:
# Say goodbye
putlog "Attempting reboot..."
reboot
} else {
putlog "ERROR could not find the utils archive"
}

Edited:
# Say goodbye
putlog "Attempting reboot..."
putlog "..not rebooting.."
exit 0
#reboot

} else {
putlog "ERROR could not find the utils archive"

}

6. Time to let TiVo update the software. Hopefully all goes well here. Keep an eye on the output and see which partition (hda4 or hda7) the new root goes to. I have actually experienced errors here that should occur when the installSw.itcl file isn’t edited, but was. A lot of people are having problems with the installSw script and I suspect that a lot of the issues stem from copying the file to a PC to edit it. You really need to be careful when you’re doing that not to screw up line endings or anything else. Maybe even more importantly, if you DO use vi, make sure not to screw up anything else in the file.


/tvbin/installSw.itcl 6.2-01-2-321 # Yes, that number from before is what you insert here to tell the TiVo, "Hey update to this software version from the MFS database".

7. All went well? I sure hope so. installSw.itcl will have installed a new root and flipped the bootpage, so if you reboot now everything will work but your system will revert to being “unhacked”. Take note of the new root ie: “Old root is on /dev/hda7, new one goes on /dev/hda4″. Hopefully you have some idea of where your hacks are, so you can make sure you get everything.


mkdir /tivo

mount /dev/hda4 /tivo # Mount the new tivo root to /tivo (hda4 or hda7).
cp -Rfpd /tivo-bin /tivo/
cp /etc/rc.d/rc.sysinit.author /tivo/etc/rc.d/
cp -Rfpd /hacks/ /tivo/ # If you have /hacks
cp -Rfpd /ptvupgrade/ /tivo/ # If you used PTVnet
mkdir /tivo/init
cp -Rfpd /init/ptvflags /tivo/init/
cp -Rfpd /var/hacks/ /tivo/ # If you have /var/hacks

** At this point you have a choice. You can either install a monte or chainload configuration, or you can boot a kernel directly. There are advantages to using the monte process, such as easily being able to drop a replacement kernel into place. If you want to use the traditional monte, continue on to step 8 and 9. If not, skip 8 and 9, and go to step 9.8.

8. Upload the new 62_init_framework_ddn.


ftp 192.168.3.105 # FTP to the IP of the tivo
cd /tivo/
put 62_init_framework_ddn.tgz

9. Unpack the init_framework and fix the bootpage. Once again, since I am assuming your system is already hacked, you should have a killhdinitrd’ed TiVo kernel in your boot partition. The nice thing is that we’re going to use this same kernel. updateroot flipped the bootpage, but all we have to do is flip it back to boot from the same kernel.


cd /tivo/
tar -zxvf 62_init_framework_ddn.tgz
bootpage -f
mv /tivo/etc/netfilter-enable /tivo/etc/netfilter-enable.not

9.8. Skip this step if you performed steps 8 and 9. You’re going to need kernel version 2.4.20 for this, more often known as the kernel from 3.1.5. The easiest way to get this is from the PTVupgrade Enhanced LBA48 CD which you probably already own. On the CD is a folder called s2_kernels, and then 3.1.5. Grab the kernel out of there, and upload it to your TiVo. This kernel already has had killhdinitrd applied to it, and is ready to go. If you are sourcing your 2.4.20 (3.1.5 tivo version) kernel from somewhere else, you will need to killhdinitrd it.


ftp 192.168.3.105 # FTP to the IP of the tivo
cd /var/packages/
put vmlinux.px


dd if=/dev/zero of=/dev/hda3 # write zeros to the boot partition
dd if=/dev/zero of=/dev/hda6

dd if=/var/packages/vmlinux.px of=/dev/hda3 # write the kernel to the boot partitions
dd if=/var/packages/vmlinux.px of=/dev/hda6
mv /tivo/etc/netfilter-enable /tivo/etc/netfilter-enable.not

10. Unless I’ve forgotten something, reboot. You’ll get a blue DirecTV screen that says “Preparing service update…this will take an hour”. This is the TiVo updating its database, and will probably take significantly less than an hour.

11. Upload superpatch and set_mrv_name


ftp 192.168.3.105 # FTP to the IP of the tivo

cd /var/packages/
put superpatch-67all-NutKase-1.0.tcl
put set_mrv_name_67.tcl

12. Telnet to the IP of your tivo. You should get a bash prompt like:


bash-2.02#

Type:

mount -o remount,rw / # TiVo mounts the drive read-only, changes would not be applied to the disk. This remounts it read-write.
cd /var/packages/
chmod 755 superpatch-67all-NutKase-1.0.tcl
./superpatch-67all-NutKase-1.0.tcl
chmod 755 set_mrv_name_67.tcl
./set_mrv_name_67.tcl YOURTIVONAME # (Type in the name for your Tivo, if you have more than 1, choose something descriptive ("Bedroom Tivo"). If you use spaces, you need quotes "around it")
mount -o remount,ro / # If this errors, go ahead and reboot anyway.

13. Reboot. That’s it.

** Additional Things You Can Do **

  • Add crond to automate running fakecall daily or other things. Keep in mind fakecall must be run weekly (or daily) to avoid the calling nag. Consider this mandatory, but it is not part of this guide. Explicit instructions courtesy of AlphaWolf.
  • USB 2.0 network modules for improved speed. See guide
  • Thanks to everyone who did the Free mini Macs offer. I got my mini a few months ago, and I love it.
  • That said, I’d like to get my hands on an iPod nano. Thanks for helping me out.
  • Change the hostname of the TiVo and the bash prompt accordingly. I like to do this so I don’t do the right command on the wrong TiVo.


    hostname "hostname of your choice without quotes" # Insert your hostname
    echo "hostname " `hostname` >>/etc/rc.d/rc.sysinit.author # Just like its written
    echo "export PS1=\"\h #\"">/etc/profile

  • Buy me a beer.
  • Offer me a job.
  • Donate to the EFF.

It doesn’t work! What should I do?


Noticing that most of the links are from DealDatabase you might be tempted to go post there and expect someone to figure out the problem for you. Fight the temptation. Re-read the guide and make sure you’ve done every step correctly. Read the threads with the linked files in them. Search the DealDatabase forum for things relative to your problem. Whatever problem you have, it is not unique to you or your setup. Someone has had it before, and a solution has been presented. Before posting, I strongly recommend reading the guidelines outlined by ESR. If and when you do post a question, post in the Newbie Forum and make sure to be extremely specific. Explain what hardware you are using, what software you are using, what you have done, and what you are trying to accomplish. If you don’t, at best you will be ignored, and at worst they will make you cry.

So easy a kid could do it!




6 August 2005 Comments Off

Fakecall Explanation

Fakecall

JohnSorTivo:

Included in AlphaWolf’s All-In-One S2 utilities is a file called ‘fakecall.tcl’, which makes the Tivo think the daily call has been successfully made. This prevents the nag screen when your phone line is not plugged in, and also enables you to setup your network after your initial install, since the Tivo first wants to make an actual call before it will let you access the network configuration options. Running fakecall.tcl satisfies this requirment, making the Tivo think the first call has been made, so that you can continue and set your network up, without actually making a real call.

It’s best to either schedule fakecall.tcl to run from a scheduled cron job, or run it in an infinite loop at system startup, using a script such as callfixsub.sh. Do a search on ‘callfixsub’ for more information if you are not running cron.

For those initially hacking their machine, while creating their rc.sysinit.author file, it’s probably not a bad idea to place a call to fakecall.tcl in rc.sysinit.author, so that fakecall.tcl gets run during the first-boot, again, enabling access to the network setup options. Note: this is of course included in the 4.x guide.

rpl adds:

fixsub aka fakecall does two things for you. It sets a flag telling the tivo that its completed guided setup, so that you do not need the initial call. It also tells the the tivo that it has successfully made a call. This prevents a nag message that starts when the tivo hasn’t made a call withing the past 30 days.

Keep in mind fakecall must be run weekly (or daily) to avoid the calling nag message. So as said above either set this up to run daily with crond or with a callsub script that runs it of a looped program.