From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from list by lists.gnu.org with archive (Exim 4.71) id 1UY87e-0007JJ-Ca for mharc-grub-devel@gnu.org; Fri, 03 May 2013 01:01:30 -0400 Received: from eggs.gnu.org ([208.118.235.92]:37456) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UY87b-0007IJ-K7 for grub-devel@gnu.org; Fri, 03 May 2013 01:01:29 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1UY87a-0001tA-M9 for grub-devel@gnu.org; Fri, 03 May 2013 01:01:27 -0400 Received: from mail-la0-x22c.google.com ([2a00:1450:4010:c03::22c]:41705) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UY87a-0001t5-F4 for grub-devel@gnu.org; Fri, 03 May 2013 01:01:26 -0400 Received: by mail-la0-f44.google.com with SMTP id ed20so1200397lab.3 for ; Thu, 02 May 2013 22:01:25 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:date:from:to:cc:subject:message-id:in-reply-to :references:x-mailer:mime-version:content-type :content-transfer-encoding; bh=0wF7FkgKwwbtqu+nHhwaFdHkX3avSHn8WTcMC9cfk9c=; b=ee9d8XKlotDlOp4g3xNeD6UGqZB8NEQQF7Z+JLcDdRPFSwjr0vKfU3q0ERFY6kW3mg R54vuKH7RmJMAKc4xxgdGHloGYl26dEZcBi2tCvDaKlxH+Z3X8/nLEqV6E8II2rYGq3Y qDgueYryHwYkGlrj1B6o2fNYIWHHNyK7X2gd4XNcrF2/9gg7KkP4iqZUhHIXdyXkG8y+ /Bjdg2Dn/jdcBYSF8DhhhMNu2aCWS5SUcOpy1rpIz2GfDBTC5236+rYzoZr5wNsJEJ0N VMExTlU6x14bMUafMpkIDwMaSaY/VrLt2qNdkkXs8JA+AsbnYwQ2k3WVWSYS3mYwM8HG Mktw== X-Received: by 10.152.21.74 with SMTP id t10mr3565133lae.52.1367557285303; Thu, 02 May 2013 22:01:25 -0700 (PDT) Received: from opensuse.site ([94.29.72.160]) by mx.google.com with ESMTPSA id w9sm3615151lbe.6.2013.05.02.22.01.24 for (version=SSLv3 cipher=RC4-SHA bits=128/128); Thu, 02 May 2013 22:01:24 -0700 (PDT) Date: Fri, 3 May 2013 09:01:23 +0400 From: Andrey Borzenkov To: The development of GNU GRUB Subject: Re: GRUB and the risk of block list corruption in extX Message-ID: <20130503090123.3b1f3c4d@opensuse.site> In-Reply-To: <51138645.4050405@ts.fujitsu.com> References: <51138645.4050405@ts.fujitsu.com> X-Mailer: Claws Mail 3.9.0 (GTK+ 2.24.14; x86_64-suse-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=KOI8-R Content-Transfer-Encoding: 8bit X-detected-operating-system: by eggs.gnu.org: Error: Malformed IPv6 address (bad octet value). X-Received-From: 2a00:1450:4010:c03::22c Cc: martin.wilck@ts.fujitsu.com X-BeenThere: grub-devel@gnu.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: The development of GNU GRUB List-Id: The development of GNU GRUB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 May 2013 05:01:29 -0000 В Thu, 07 Feb 2013 11:47:33 +0100 Martin Wilck пишет: > 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.