All of lore.kernel.org
 help / color / mirror / Atom feed
From: James Courtier-Dutton <james.dutton@gmail.com>
To: grub-devel <grub-devel@gnu.org>
Subject: Protection of boot sector and embedded area
Date: Sat, 26 Sep 2009 09:28:12 +0100	[thread overview]
Message-ID: <ad2655cb0909260128y1fe1902bm11dcdafebbba8906@mail.gmail.com> (raw)

Hi

Is there a setting for grub-install/grub-setup where, if set, will
never actually over write the boot sector and embedded area of my HD?
I don't mind grub.conf being written to, I just do not want the boot
up executables written to.
For example, if I have an Ubuntu install, and the grub package gets
upgraded, is there a way to stop the automatic update from attacking
the boot and embedded area of my HD?

Kind Regards

James



             reply	other threads:[~2009-09-26  8:28 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-26  8:28 James Courtier-Dutton [this message]
2009-09-26  8:57 ` Protection of boot sector and embedded area Colin Watson
2009-09-26  9:07   ` James Courtier-Dutton
2009-09-26  9:13     ` Colin Watson
2009-09-26 10:40       ` James Courtier-Dutton
2009-09-26 10:47         ` Felix Zielcke
2009-09-26 14:49     ` Vladimir 'phcoder' Serbinenko
2009-09-26 21:57       ` James Courtier-Dutton
2009-09-26 22:07         ` Vladimir 'phcoder' Serbinenko
2009-09-26 22:47           ` James Courtier-Dutton
2009-09-26 23:01             ` Vladimir 'phcoder' Serbinenko
2009-09-27 11:37             ` Michal Suchanek
2009-09-27 12:21               ` James Courtier-Dutton
2009-09-27 12:41                 ` Vladimir 'phcoder' Serbinenko
2009-09-26 22:12         ` Vladimir 'phcoder' Serbinenko

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=ad2655cb0909260128y1fe1902bm11dcdafebbba8906@mail.gmail.com \
    --to=james.dutton@gmail.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.