From: neozeed@gmail.com (Jason Stevens)
Subject: [TUHS] dump(8) compatibility
Date: Mon, 15 Feb 2010 00:18:12 -0500 [thread overview]
Message-ID: <46b366131002142118p4157cd7m6bc5e171692aae3@mail.gmail.com> (raw)
In-Reply-To: <A2F25A9A-A2F6-438F-AB2F-F060C8B600CF@bsdimp.com>
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.....
On Mon, Feb 15, 2010 at 12:05 AM, Warner Losh <imp at bsdimp.com> wrote:
> Tar and cpio at least have a standard, well understood format. Dump was
> always only defined by the source.
>
> Warner
>
>
>
> On Feb 14, 2010, at 7:27 PM, Larry McVoy <lm at bitmover.com> wrote:
>
> It used to be the case that dump was completely interchangeable
>>> between the different BSDs, but software drift has rendered that not
>>> the case anymore.
>>>
>>
>> Which is why we (BitKeeper guys) don't even trust cpio/tar/etc. Wrote our
>> own, works everywhere including windows.
>> --
>> ---
>> Larry McVoy lm at bitmover.com
>> http://www.bitkeeper.com
>>
>>
>> _______________________________________________
> TUHS mailing list
> TUHS at minnie.tuhs.org
> https://minnie.tuhs.org/mailman/listinfo/tuhs
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20100215/6e6ab2b4/attachment.html>
-------------- next part --------------
_______________________________________________
TUHS mailing list
TUHS at minnie.tuhs.org
https://minnie.tuhs.org/mailman/listinfo/tuhs
next prev parent reply other threads:[~2010-02-15 5:18 UTC|newest]
Thread overview: 64+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-21 10:26 [TUHS] Irwin 285 Sergey Lapin
2010-01-21 10:51 ` Brantley Coile
2010-01-21 11:19 ` Jochen Kunz
2010-01-21 11:32 ` Wilko Bulte
2010-01-21 12:07 ` Sergey Lapin
2010-01-21 12:37 ` Jason Stevens
2010-01-21 13:02 ` Wilko Bulte
2010-01-21 16:50 ` Jochen Kunz
2010-01-21 17:11 ` Jochen Kunz
2010-01-21 17:37 ` M. Warner Losh
2010-01-21 17:41 ` Sergey Lapin
2010-01-21 19:00 ` Jochen Kunz
2010-01-21 19:10 ` Al Kossow
2010-01-21 19:36 ` Jochen Kunz
2010-01-21 19:41 ` Wilko Bulte
2010-01-21 19:45 ` John Cowan
2010-01-21 18:59 ` Wilko Bulte
2010-01-21 19:48 ` Jochen Kunz
2010-01-21 19:56 ` Wilko Bulte
2010-01-21 19:58 ` Larry McVoy
2010-01-21 20:00 ` Wilko Bulte
2010-01-21 20:11 ` Larry McVoy
2010-01-21 20:26 ` Jason Stevens
2010-01-21 20:41 ` Wilko Bulte
2010-01-21 20:44 ` Larry McVoy
2010-01-21 21:00 ` Wilko Bulte
2010-01-21 21:01 ` Larry McVoy
2010-01-21 21:36 ` lyricalnanoha
2010-01-21 22:15 ` Larry McVoy
2010-01-21 22:22 ` M. Warner Losh
2010-01-22 9:14 ` Jochen Kunz
2010-01-22 9:34 ` Wilko Bulte
2010-01-22 10:15 ` Jochen Kunz
2010-01-22 10:46 ` Wilko Bulte
2010-01-22 11:06 ` Jochen Kunz
2010-01-22 11:12 ` Wilko Bulte
2010-01-22 15:38 ` Larry McVoy
2010-01-22 16:52 ` Jochen Kunz
2010-01-22 16:55 ` Wilko Bulte
2010-01-21 20:46 ` Jason Stevens
2010-01-21 22:15 ` Aaron J. Grier
2010-01-21 22:57 ` Wilko Bulte
2010-01-21 20:36 ` Wilko Bulte
2010-01-21 20:44 ` Corey Lindsly
2010-01-21 21:45 ` Wilko Bulte
2010-01-22 0:36 ` [TUHS] Backup software (was: Irwin 285) Greg 'groggy' Lehey
2010-01-22 0:48 ` Jason Stevens
2010-01-28 20:27 ` Brad Spencer
2010-02-12 17:03 ` Tim Bradshaw
2010-02-15 1:19 ` [TUHS] dump(8) compatibility (was: Backup software (was: Irwin 285)) Greg 'groggy' Lehey
2010-02-15 1:24 ` Jason Stevens
2010-02-15 1:30 ` [TUHS] dump(8) compatibility M. Warner Losh
2010-02-15 2:27 ` Larry McVoy
2010-02-15 5:05 ` Warner Losh
2010-02-15 5:18 ` Jason Stevens [this message]
2010-01-21 20:33 ` [TUHS] Irwin 285 Jochen Kunz
2010-01-21 20:44 ` Wilko Bulte
2010-01-21 20:47 ` Larry McVoy
2010-01-22 9:23 ` Jochen Kunz
2010-01-22 9:32 ` Wilko Bulte
2010-01-22 0:38 ` [TUHS] Tape backups? (was: Irwin 285) Greg 'groggy' Lehey
2010-01-21 20:18 ` [TUHS] Irwin 285 Jochen Kunz
2010-01-21 12:05 ` Andrzej Popielewicz
2010-01-21 12:12 ` Sergey Lapin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=46b366131002142118p4157cd7m6bc5e171692aae3@mail.gmail.com \
--to=neozeed@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).