From: "Theodore Y. Ts'o" <tytso@mit.edu>
To: Lukas Czerner <lczerner@redhat.com>
Cc: linux-ext4@vger.kernel.org
Subject: Re: State of dump utility
Date: Fri, 2 Oct 2020 11:17:24 -0400 [thread overview]
Message-ID: <20201002151724.GT23474@mit.edu> (raw)
In-Reply-To: <20201002120158.uyyx3cg5gdeoe665@work>
On Fri, Oct 02, 2020 at 02:01:58PM +0200, Lukas Czerner wrote:
>
> Thanks Ted, you made some good points and while there are some good
> ideas for the future, there is no place for dump there. I think we're in
> agreement to pull the plug on dump.
I think the only strong argument for dump/restore is that there might
be some crazy^H^H^H^H^H^H dedicated hobbiests over at The Unix
Historical Society who might find a 9-track tape with some 2.10 BSD
backup on it, and dump/restore is format compatible with it. So
_restore_ might be interesting for some of those folks. Then again,
they'd probably prefer to actually restore it on their 2.10 BSD system
running on a PDP-11 emulator.... so we're probably good. :-)
- Ted
next prev parent reply other threads:[~2020-10-02 15:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-29 14:37 State of dump utility Lukas Czerner
2020-09-30 2:06 ` Theodore Y. Ts'o
2020-10-02 12:01 ` Lukas Czerner
2020-10-02 15:17 ` Theodore Y. Ts'o [this message]
2020-10-02 12:15 ` Christoph Hellwig
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=20201002151724.GT23474@mit.edu \
--to=tytso@mit.edu \
--cc=lczerner@redhat.com \
--cc=linux-ext4@vger.kernel.org \
/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