From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1Mrc2Z-00029m-2d for mharc-grub-devel@gnu.org; Sat, 26 Sep 2009 14:30:39 -0400 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Mrc2W-00027N-B9 for grub-devel@gnu.org; Sat, 26 Sep 2009 14:30:36 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Mrc2P-00021b-ML for grub-devel@gnu.org; Sat, 26 Sep 2009 14:30:33 -0400 Received: from [199.232.76.173] (port=58029 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Mrc2P-00021R-FR for grub-devel@gnu.org; Sat, 26 Sep 2009 14:30:29 -0400 Received: from fg-out-1718.google.com ([72.14.220.156]:43130) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1Mrc2P-0006Fm-25 for grub-devel@gnu.org; Sat, 26 Sep 2009 14:30:29 -0400 Received: by fg-out-1718.google.com with SMTP id e21so374049fga.12 for ; Sat, 26 Sep 2009 11:30:28 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :user-agent:mime-version:to:subject:references:in-reply-to :content-type:content-transfer-encoding; bh=Y8rLTShEFFbO23HF3DOvYAPTV4pRSksHoqErgut0BLg=; b=IIxCLjYYMpd1cJvLNbmDPmiaNCJ0JgswLjf52DUUHcWnFqJ+lmZ8+AaEM3cLBlg94d G0QzKVBsLJ34k7qkuyqvmnqT3aRqtnSpJ71k5c9qLxdqEZIHmOYogdfQ30vvY1kMiJQ2 hK7qxW9Obcr+zwPZoXhEKxt0sHBFPl7QiljoU= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; b=Xw7d6WkSEqgSy81sdHg7F4O8/ClxhXHkcOZbVRcNIYB95AtvXLgYdOK+kM6R0hdqRi JtK9WTdrhaJ4fuW4ZfVh67R18o0jYcWXv5nDO1ZYb2WCmUxS1q5xSLTVhf3ldTxm3cF5 5rt6S61+v0buJKyMiicY6hTu2xo/Z5u4dS9gI= Received: by 10.86.221.25 with SMTP id t25mr2029139fgg.19.1253989828541; Sat, 26 Sep 2009 11:30:28 -0700 (PDT) Received: from ?129.132.210.210? (vpn-global-dhcp3-210.ethz.ch [129.132.210.210]) by mx.google.com with ESMTPS id l12sm2047013fgb.14.2009.09.26.11.30.27 (version=TLSv1/SSLv3 cipher=RC4-MD5); Sat, 26 Sep 2009 11:30:27 -0700 (PDT) Message-ID: <4ABE2A10.2010302@gmail.com> Date: Sat, 26 Sep 2009 16:49:52 +0200 From: Vladimir 'phcoder' Serbinenko User-Agent: Mozilla-Thunderbird 2.0.0.22 (X11/20090701) MIME-Version: 1.0 To: The development of GRUB 2 References: <20090926085720.GV13423@riva.ucam.org> In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.6 (newer, 2) Subject: Re: Protection of boot sector and embedded area X-BeenThere: grub-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: The development of GRUB 2 List-Id: The development of GRUB 2 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 26 Sep 2009 18:30:37 -0000 James Courtier-Dutton wrote: > 2009/9/26 Colin Watson : > >> On Sat, Sep 26, 2009 at 09:28:12AM +0100, James Courtier-Dutton wrote: >> >>> 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? >>> >> At the moment, this is a recipe for GRUB becoming unusable, as the >> interface between the core image and grub.cfg is not yet stable. As >> such, I expect that the Ubuntu package will be changing to make this >> harder to do by accident. >> >> > I suppose I have a special case. > My HD already has a custom boot sector and embedded area doing > something else. So I cannot install grub there at all. > It's generally a bad idea to chase grub out of MBR+embed area. It often results in unreliable configurations. Could you detail your usecase so we can seek for a bettere solution? > I am currently installing grub onto a usb stick and booting Linux from > the usb stick, with the usb stick just doing the grub bit for me. > I want to make sure that if I do automatic upgrades in ubuntu, it will > never accidentally wipe the custom boot sector and embedded areas of > my HD. > I will manually do grub-install to update the grub on my usb stick. > > > _______________________________________________ > Grub-devel mailing list > Grub-devel@gnu.org > http://lists.gnu.org/mailman/listinfo/grub-devel > >