If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.

"tivopart revalidate" does exactly what compwiz described; it requires no kernel patch.

Ah? Interesting. My apologies, then.

But compwiz said "tivopart reinitialize", which sounds like something else. ("Initialize" is a common term for "format".) I seem to have an old version of tivopart here that lacks either of these options.

But compwiz said "tivopart reinitialize", which sounds like something else. ("Initialize" is a common term for "format".)

Yeah, he meant 'revalidate', which alters the in-memory partition table to change the signature from a 'tivo' signature to a 'mac' signature, and the block size to 512, which is a pretty nifty stunt, if you ask me .

I seem to have an old version of tivopart here that lacks either of these options.

But compwiz said "tivopart reinitialize", which sounds like something else. ("Initialize" is a common term for "format".) I seem to have an old version of tivopart here that lacks either of these options.

It only looks at the first letter of the command, so either will work. I do believe the initial release lacked this feature.

What it does is quite simple: it uses functions from the pdisk code to read and interpret the partition table, then uses the BLKPG ioctls to change the kernel's in-memory partition structures. I implemented this so that I could make a one-step reimaging script, which uses mfsrestore to write out MFS, tivopart to move around the other partitions and revalidate the partition table, then mke2fs, tar, etc. to set up the ext2 filesystems.