From: Robert Millan <rmh@aybabtu.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: [PATCH]: Save boot record before writing to the dest_drive
Date: Sun, 20 Sep 2009 13:22:14 +0200 [thread overview]
Message-ID: <20090920112214.GA3971@thorin> (raw)
In-Reply-To: <20090919220917.GE13423@riva.ucam.org>
On Sat, Sep 19, 2009 at 11:09:17PM +0100, Colin Watson wrote:
> On Sat, Sep 19, 2009 at 11:10:49PM +0200, Robert Millan wrote:
> > I'm sorry, but I really see very limited usefulness in this. It's only
> > potentially useful to expert users, but those should know how to backup
> > sectors in their disk already.
>
> Of course, like many restore facilities, it's only useful if you
> remembered or realised that you needed to do the backup before the data
> was overwritten ...
>
> It would be nice to have a straightforward answer to the sort of bug
> report that goes "argh, I installed Debian/Ubuntu and it ate the special
> magic boot loader I carefully installed there five years ago", I must
> admin.
So your point is that if backup is done automatically, this would be useful
when dealing with users who didn't plan ahead?
Seems reasonable.
--
Robert Millan
The DRM opt-in fallacy: "Your data belongs to us. We will decide when (and
how) you may access your data; but nobody's threatening your freedom: we
still allow you to remove your data and not access it at all."
next prev parent reply other threads:[~2009-09-20 11:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-12 14:05 [PATCH]: Save boot record before writing to the dest_drive kashyap garimella
2009-09-14 15:35 ` Robert Millan
2009-09-14 15:44 ` kashyap garimella
2009-09-19 21:10 ` Robert Millan
2009-09-19 22:09 ` Colin Watson
2009-09-20 6:50 ` richardvoigt
2009-09-20 11:22 ` Robert Millan [this message]
2009-09-23 8:08 ` Mikko Rantalainen
2009-09-24 15:45 ` kashyap garimella
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=20090920112214.GA3971@thorin \
--to=rmh@aybabtu.com \
--cc=grub-devel@gnu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.