
Originally Posted by
tiver
Can you elaborate on the first method you talk about - is /etc/rc.d/StageE_PreApplication/rc.Sequence_500.CheckForSoftwareUpgrade.sh partof the tivo hacks, or is that an official tivo shell script ? I can't get into my tivo right now, since its de-hacked, but what should I look at in those scripts when I do ?
it's a native tivo script. here's the contents :
Code:
if [ "$upgradesoftware" = false ]; then
echo "Not upgrading software"
else
emergency=""
if [ "$EMERGENCY_REINSTALL" = 1 ]; then
emergency="-e"
fi
/tvbin/checkForSwInstall $emergency
if [ $? -eq 0 ]; then
#
# Time to install s/w
#
/tvbin/osdwriter /tvbin/InstallingSoftware.png
echo -n "INSTALLING" >> /dev/ircatch0 2>/dev/null
/tvbin/tivosh /tvbin/installSw.itcl
fi
export -n EMERGENCY_REINSTALL
fi
as you can see, there's plenty of ways to edit it. Or if you rename installSw.itcl, then the tivo can't ever run it, since it won't even know what its name is.
A more general question - is this method something I could theoretically just leave in place and ignore updates _forever_ ? I don't plan on doing this, of course, but I want to get a sense for how bulletproof I can make my system - in case I am on an extended trip again and can't deal with my tivo ...
you couldn't leave in place for forever, since you'd stop receiving guide data at some point, but it should hold it off long enough for you to rehack it without pulling the drive.