All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Vladimir 'φ-coder/phcoder' Serbinenko" <phcoder@gmail.com>
To: grub-devel@gnu.org
Subject: Re: [RFC] Detect other software using embedding area
Date: Tue, 31 Aug 2010 18:17:42 +0200	[thread overview]
Message-ID: <4C7D2B26.5030405@gmail.com> (raw)
In-Reply-To: <AANLkTi=g-7F2wdE7gYp5=LMmr1Ac5rxGvYb8Hq493q+K@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1922 bytes --]

On 08/31/2010 05:36 PM, Brendan Trotter wrote:
> Hi,
>
> On Tue, Aug 31, 2010 at 8:28 PM, Colin Watson <cjwatson@ubuntu.com> wrote:
>   
>> When I blogged about this recently (and rather unexpectedly ended up on
>> Slashdot), several people followed up to say that GRUB shouldn't be
>> using the embedding area because it was never defined to be used for
>> anything in particular and has no protocol for arbitrating among
>> conflicts like this.
>>     
> Unfortunately, where the PC BIOS is concerned a lot of things are de
> facto standards, rather than actual standards; but I've always held a
> far simpler view: The MBR and the remaining sectors in the first track
> (before the start of the first partition) are reserved for the sole
> use of the "boot manager". If GRUB is the boot manager, then no OS
> (and no application running under any OS) has the right to touch these
> sectors; and the opposite is also true - e.g. if GRUB is not the MBR
> (e.g. GRUB is chain-loaded by something else) then GRUB has no right
> to touch any of these sectors.
>
>   
I completely agree with this point of view.
> If applications running on Windows are causing problems (overwriting
> something they have no right to touch), then the best solution would
> be a public web page (maybe in the GRUB wiki?) that explains the
> problem and lists which applications are buggy/broken crap...
>
>   
List of such software would be a good thing. However relying on it as
the sole solution supposes that the user is concious and searches the
real reason. However this expectation however logical it seems is
completely irrealistic given our userbase.
> Cheers,
>
> Brendan
>
> _______________________________________________
> Grub-devel mailing list
> Grub-devel@gnu.org
> http://lists.gnu.org/mailman/listinfo/grub-devel
>
>   


-- 
Regards
Vladimir 'φ-coder/phcoder' Serbinenko



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 294 bytes --]

      reply	other threads:[~2010-08-31 16:18 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-31 10:58 [RFC] Detect other software using embedding area Colin Watson
2010-08-31 12:54 ` Thomas Schmitt
2010-08-31 13:11   ` Colin Watson
2010-09-05 15:14   ` C. P. Ghost
2010-09-05 23:31     ` richardvoigt
2010-08-31 13:45 ` BVK Chaitanya
2010-08-31 13:54   ` Colin Watson
2010-08-31 15:36 ` Brendan Trotter
2010-08-31 16:17   ` Vladimir 'φ-coder/phcoder' Serbinenko [this message]

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=4C7D2B26.5030405@gmail.com \
    --to=phcoder@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.