15 Mar
2007
15 Mar
'07
12:58 a.m.
On 15/3/07 05:16, "Jim Leonard" <trixter at oldskool.org> wrote:
Adrian Graham wrote:
I was kind of taking the simplistic view that each file had a standard sized
header that at least had a magic number* and some indication of length of
said file. I can also see that it might just read-until-EOF so maybe I was
crediting it with too much intelligence.
*osf1/tru64 files have a magic number in the header that describes the file
type which you can determine with the 'file' command. Since Tru64 is part
BSD and part SYSV I thought said behaviour must've come from one of those.
--
Adrian/Witchy
Binary Dinosaurs creator/curator
Www.binarydinosaurs.co.uk - the UK's biggest private home computer
collection?
On 14/3/07 18:59, "Jim Leonard"
<trixter at oldskool.org> wrote:
How would cat know what part of the stream was the header? Were you
talking about *nix cat or some other cat? Adrian Graham wrote:
Ah, my bad. I naturally assumed that cat would strip those off and just have But by cat-ing several mpegs together you DO end
up with a single header,
No, you end up with an invalid target with multiple
beginning-of-file
headers throughout the file.