From: Andrey Borzenkov <arvidjaar@gmail.com>
To: The development of GNU GRUB <grub-devel@gnu.org>
Cc: martin.wilck@ts.fujitsu.com
Subject: Re: GRUB and the risk of block list corruption in extX
Date: Fri, 3 May 2013 09:01:23 +0400 [thread overview]
Message-ID: <20130503090123.3b1f3c4d@opensuse.site> (raw)
In-Reply-To: <51138645.4050405@ts.fujitsu.com>
В Thu, 07 Feb 2013 11:47:33 +0100
Martin Wilck <martin.wilck@ts.fujitsu.com> пишет:
> Hello,
>
> this is a question about the long-running topic of installing GRUB in
> partitions or partitionless disks.
>
Here is example how using filesystem blocklists may lead to unbootable
system without any extX corruption involved.
- user sets up multiboot system with Windows as primary bootloader
- standard technique to add Linux loaders has always been - copy
partition boot sector and "launch" it from Windows loader
- user copies Linux partition boot sector which points to core.imng
absolute disk position
- user updates grub in Linux. core.img is rewritten and its position
changes
- next time user tries to boot Linux (s)he gets blinking cursor
So *any* third party bootloader that relies on being able to
"chainload" *copy* of boot sector will give you the same issue.
next prev parent reply other threads:[~2013-05-03 5:01 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-07 10:47 GRUB and the risk of block list corruption in extX Martin Wilck
2013-02-08 11:44 ` Martin Wilck
2013-02-08 16:57 ` Vladimir 'phcoder' Serbinenko
2013-02-08 17:17 ` Vladimir 'phcoder' Serbinenko
2013-02-08 17:17 ` Martin Wilck
2013-02-08 18:42 ` Lennart Sorensen
2013-02-08 18:56 ` Bruce Dubbs
2013-02-08 18:58 ` Lennart Sorensen
2013-02-08 19:11 ` Andrey Borzenkov
2013-02-18 15:42 ` Martin Wilck
2013-02-09 6:22 ` Chris Murphy
2013-02-18 17:16 ` Martin Wilck
2013-02-18 21:07 ` Chris Murphy
2013-02-19 5:02 ` Andrey Borzenkov
2013-02-19 6:24 ` Chris Murphy
2013-02-19 8:43 ` Michael Chang
2013-02-19 9:06 ` Vladimir 'φ-coder/phcoder' Serbinenko
2013-02-19 18:54 ` Chris Murphy
2013-02-19 8:47 ` Martin Wilck
2013-02-19 18:56 ` Chris Murphy
2013-02-19 19:46 ` Martin Wilck
2013-02-19 9:37 ` Vladimir 'φ-coder/phcoder' Serbinenko
2013-02-19 12:58 ` Martin Wilck
2013-02-19 15:48 ` Vladimir 'φ-coder/phcoder' Serbinenko
2013-02-19 17:17 ` Martin Wilck
2013-02-19 5:26 ` Andrey Borzenkov
2013-02-19 10:54 ` Martin Wilck
2013-05-03 5:01 ` Andrey Borzenkov [this message]
2013-05-03 8:21 ` Martin Wilck
2013-05-03 19:21 ` Dr. Tilmann Bubeck
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=20130503090123.3b1f3c4d@opensuse.site \
--to=arvidjaar@gmail.com \
--cc=grub-devel@gnu.org \
--cc=martin.wilck@ts.fujitsu.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).