On Mon, Sep 14, 2009 at 09:14:49PM +0530, kashyap garimella wrote: > On Mon, Sep 14, 2009 at 9:05 PM, Robert Millan <r...@aybabtu.com> wrote: > > > On Sat, Sep 12, 2009 at 07:35:45PM +0530, kashyap garimella wrote: > > > Greetings! > > > > > > I have added the following new features: > > > > > > 1) when grub-setup runs, it automatically stores the areas of (mbr + > > embed) > > > region, which are overwritten, into the file (in the following specified > > > format) in root directory. > > > > > > 2) grub-setup can restore the stored mbr in the following format back to > > > destination drive: > > > > Thanks for your interest, but I really think this is overkill. Users would > > still need dd(1) to restore those images, so if they know dd(1), why can't > > they just use that to back them up in first place? > > > Sir, > > I also added a restore option (grub-setup --restore dest_drive). A dd needs > to be done explicitly. But with this patch, it will (by default) store the > mbr and the areas in embed region ( which are written by grub ). And with > the backup file, you can restore > from a live cd also. The backup file contains the start sector and the > length of the core image.
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. But if others reading this think differently, please let it be known... -- 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." _______________________________________________ Grub-devel mailing list Grub-devel@gnu.org http://lists.gnu.org/mailman/listinfo/grub-devel
