Hi Guys, thank you for your answers.... , much appreciated
Yeah J65nko, I did realise about the "#" not being part of the command
Just to quickly answer your suggestion...
mount -t ufs -o ro /dev/da0s1 /mnt
ERROR : mount: /dev/da0S1 : Invalid argument
Is there an entry for 'da0s1' in "/dev/" ? – Yes, same as per your listing also
You also could try to leave out the -t ufs part.
As per earlier , ERROR : mount: /dev/da0S1 : Invalid argument
dump -0af /colin /dev/da0s1 - comes back with.....
DUMP: Date of this level 0 dump: Fri Feb 25 09:18:48 2011
DUMP: Date of last level 0 dump: the epoch
DUMP: Dumping /dev/da0s1 to /colin
DUMP: Cannot find file system superblock
DUMP: The ENTIRE dump is aborted
Like I said at the start, I think the file system is supported by FreeBSD, as the TV's licence has BSD written all over it, but it does state that you will not be able to read it on anything else.... I think there is some kind pof protective rights DRM going on, but I don't think the data is encrytped itself, I think it's just been cleverly displaced or offset in someway form how a standard disk can be mounted... but my guess is that, if the TV can read/write to it, then there must be also some clever way of getting to it....
Is there a hex dump utility that might be able to check the dev out sin some way, that it doesn't need to be mounted first... just guessing at my own solution there... welcome to try anything else....? :-)
Cheers
Colin