mirror of https://github.com/elitak/mfs-utils.git
1125e1269c | ||
---|---|---|
contrib | ||
CHANGES | ||
Makefile | ||
NowShowing.c | ||
NowShowing.tcl | ||
README.FIRST | ||
README.Jamie | ||
README.MFS_DEVICE | ||
README.OS_X | ||
README.adh | ||
README.jdiner | ||
README.jdiner2 | ||
README.jdiner3 | ||
README.randomramblings | ||
README.tridge | ||
README_sd-h400_unlock.txt | ||
attribute.c | ||
attribute.h | ||
bitmap.c | ||
ciphercheck.c | ||
compat.h | ||
crc.c | ||
credits.c | ||
export.c | ||
generate_NowShowing.c | ||
generate_xml.c | ||
index.html | ||
io.c | ||
log.c | ||
log.h | ||
make-preload-schema.pl | ||
mfs.c | ||
mfs.h | ||
mfs_bitmap.c | ||
mfs_burstcmds.c | ||
mfs_dump.c | ||
mfs_dumpobj.c | ||
mfs_dumpschema.c | ||
mfs_export.sh | ||
mfs_findzero.c | ||
mfs_ftp.jamie.patch | ||
mfs_ftp.jbuehl.patch | ||
mfs_getslice.c | ||
mfs_import.c | ||
mfs_info.c | ||
mfs_ls.c | ||
mfs_poke.c | ||
mfs_purge.c | ||
mfs_stream.sh | ||
mfs_streams.c | ||
mfs_tarstream.sh | ||
mfs_tmfstream.sh | ||
mfs_tzoffset.c | ||
mfs_uberexport.c | ||
mkpkg.sh | ||
mkproto.awk | ||
object.c | ||
partition.c | ||
pri.c | ||
query.c | ||
read_xml.c | ||
schema-7.1a-02.txt | ||
schema-7.3.1.txt | ||
schema-merged-9.3.txt | ||
schema.c | ||
schema.tcl | ||
sd-h400_unlock.c | ||
tar.c | ||
tar.h | ||
tserver.c | ||
ty_audio.c | ||
tzoffset.c | ||
util.c | ||
vplay.c | ||
vplayer.c | ||
vserver.c | ||
vsplit.c |
README.tridge
use mfs_streams to find what video stream files are on your tivo use vplay to "play" with that fsid to a file or device use vplayer to play files remotely mfs_ls lists directories. Use -R for recursive listing. mfs_dumpobj dumps a TiVo object mfs_export exports files (of any type) from the mfs to a unix file mfs_info dumps some basic info on your fs and a fsid mfs_dump dumps some sectors (useful for debugging) The Makefile builds both i386 and tivo binaries. To build just the i386 binaries run "make host". Similarly for "make tivo". A simple "make" will build everything. Running the tivo binaries is easy, just copy them to your tivo and make sure MFS_DEVICE is set correctly before starting them. You should find that MFS_DEVICE is set by the tivo startup scripts, usually to /dev/hda10. Running the binaries on a Linux PC is a bit different. The main thing you need to get right is the MFS_DEVLIST environment variable. Setting that allows you to run mfs commands against either a locally accesssible TiVo drive or a remote TiVo accessed across a TCP link. To run on a local drive (or files containing images of a drive) you set MFS_DEVLIST to a space separated list of files/devices containing the MFS filesystem. For example: export MFS_DEVLIST="/backup/hda10 /backup/hda11_aa /backup/hda11_ab" (Don't forget the export!) Then run the mfs_* commands as usual. To run on a remote TiVo you need to start a tivo vserver binary on the TiVo. Then on your Linux PC set MFS_DEVLIST to :hostname where hostname is the IP or hostname of your TiVo. Then run the mfs commands as usual. You can also point MFS_DEVLIST at a raw TiVo disk, and the mfs code will look in the TiVo partition table to find the MFS partitions.