reminds me of the tar changes with the advent of gnutar... boy have I had a lot of fun transporting files to find out when extracting it creates the directories as files.....<div><br></div><div><br><div class="gmail_quote">
On Mon, Feb 15, 2010 at 12:05 AM, Warner Losh <span dir="ltr">&lt;<a href="mailto:imp@bsdimp.com">imp@bsdimp.com</a>&gt;</span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Tar and cpio at least have a standard, well understood format. Dump was always only defined by the source.<br><font color="#888888">
<br>
Warner</font><div><div></div><div class="h5"><br>
<br>
<br>
On Feb 14, 2010, at 7:27 PM, Larry McVoy &lt;<a href="mailto:lm@bitmover.com" target="_blank">lm@bitmover.com</a>&gt; wrote:<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
It used to be the case that dump was completely interchangeable<br>
between the different BSDs, but software drift has rendered that not<br>
the case anymore.<br>
</blockquote>
<br>
Which is why we (BitKeeper guys) don&#39;t even trust cpio/tar/etc.  Wrote our<br>
own, works everywhere including windows.<br>
-- <br>
---<br>
Larry McVoy                lm at <a href="http://bitmover.com" target="_blank">bitmover.com</a>           <a href="http://www.bitkeeper.com" target="_blank">http://www.bitkeeper.com</a><br>
<br>
<br>
</blockquote>
_______________________________________________<br>
TUHS mailing list<br>
<a href="mailto:TUHS@minnie.tuhs.org" target="_blank">TUHS@minnie.tuhs.org</a><br>
<a href="https://minnie.tuhs.org/mailman/listinfo/tuhs" target="_blank">https://minnie.tuhs.org/mailman/listinfo/tuhs</a><br>
</div></div></blockquote></div><br></div>