grub-devel.gnu.org archive mirror
 help / color / mirror / Atom feed
From: Phillip Susi <psusi@cfl.rr.com>
To: The development of GNU GRUB <grub-devel@gnu.org>
Cc: "Vladimir 'φ-coder/phcoder' Serbinenko" <phcoder@gmail.com>
Subject: Re: Guidance on conflicts between GNU GRUB and proprietary software
Date: Tue, 28 Sep 2010 15:22:13 -0400	[thread overview]
Message-ID: <4CA24065.9030608@cfl.rr.com> (raw)
In-Reply-To: <4CA23C71.9040601@gmail.com>

On 9/28/2010 3:05 PM, Vladimir 'φ-coder/phcoder' Serbinenko wrote:
> Using an embedding partition on msdos as an optional alternative (not as
> replacement) to MBR gap is a clear possibility, good idea and was
> proposed before but details are very unclear. Like:
> - How to create such partition

The same way you create any other partition?

> - How does grub find it and ensures that it's an embedding partition?
> Any false positive will result in data loss. Obviously no msdos type is
> completely unused by now so it's not a way.

There seem to be quite a few left that are at least unknown to linux
fdisk.  If you really want to make sure, then you can require a grub
signature in the starting sector of the partition.  Also this step would
usually be done by the installer, which would know that the partition is
a grub partition since it just created it.


  parent reply	other threads:[~2010-09-28 19:22 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-23 22:19 Guidance on conflicts between GNU GRUB and proprietary software Colin Watson
2010-09-24  0:27 ` Lennart Sorensen
2010-09-24 14:09   ` Richard Stallman
2010-09-28  4:44     ` richardvoigt
2010-09-28  4:55       ` Bogdan
2010-09-28  8:04         ` Colin Watson
2010-09-28  9:10           ` Bogdan
2010-09-28  9:41             ` Colin Watson
2010-09-28  9:51               ` Bogdan
2010-09-28 10:25                 ` Colin Watson
2010-09-28 10:40                   ` Bogdan
2010-09-28 11:49                     ` Colin Watson
2010-09-28 14:50             ` Lennart Sorensen
2010-09-28 15:05               ` Bogdan
2010-09-28 18:18               ` Grub2 Install Image Dee Sharpe
2010-09-28 21:45                 ` Dmitry Ilyin
2010-09-28 15:40           ` Guidance on conflicts between GNU GRUB and proprietary software Phillip Susi
2010-09-28 16:18             ` Colin Watson
2010-09-28 17:52               ` Phillip Susi
2010-09-28 19:05           ` Vladimir 'φ-coder/phcoder' Serbinenko
2010-09-28 19:15             ` Lennart Sorensen
2010-09-28 19:43               ` Vladimir 'φ-coder/phcoder' Serbinenko
2010-09-28 20:07                 ` Lennart Sorensen
2010-09-28 20:58                   ` Vladimir 'φ-coder/phcoder' Serbinenko
2010-09-28 21:15                     ` Lennart Sorensen
2010-09-28 21:34                       ` Vladimir 'φ-coder/phcoder' Serbinenko
2010-09-28 19:22             ` Phillip Susi [this message]
2010-09-28 21:46             ` Grégoire Sutre
2010-09-28 22:11               ` Vladimir 'φ-coder/phcoder' Serbinenko
2010-09-29 10:00                 ` Grégoire Sutre
2010-09-28 19:11           ` Vladimir 'φ-coder/phcoder' Serbinenko
2010-09-28 14:57       ` Lennart Sorensen
2010-09-28  9:01     ` Vladimir 'φ-coder/phcoder' Serbinenko
2010-09-24 10:57 ` Brendan Trotter

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=4CA24065.9030608@cfl.rr.com \
    --to=psusi@cfl.rr.com \
    --cc=grub-devel@gnu.org \
    --cc=phcoder@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).