From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1LlOWI-0002Gc-O4 for mharc-grub-devel@gnu.org; Sun, 22 Mar 2009 10:19:22 -0400 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1LlOWD-0002EN-Sv for grub-devel@gnu.org; Sun, 22 Mar 2009 10:19:18 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1LlOW9-0002CT-8I for grub-devel@gnu.org; Sun, 22 Mar 2009 10:19:17 -0400 Received: from [199.232.76.173] (port=54788 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1LlOW9-0002CP-2k for grub-devel@gnu.org; Sun, 22 Mar 2009 10:19:13 -0400 Received: from fg-out-1718.google.com ([72.14.220.159]:22514) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1LlOW8-00080u-DP for grub-devel@gnu.org; Sun, 22 Mar 2009 10:19:12 -0400 Received: by fg-out-1718.google.com with SMTP id 19so465503fgg.7 for ; Sun, 22 Mar 2009 07:19:11 -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=JcAr5Nkggz9sT9Y322lvA3MRc0VB2ZrmtgzRJ1+/5io=; b=bXYTSJpXDowx7BqdEDiYnN9xd8nk3NjDprSyzPYjOQXVnGYDJP+z82rI9z1O81Wy/v aiPUt/H7236AK8LOYWCqiV2VI70rSRfrl1APeTvaf52rNzoQHIwE0qbKzBHY9E7kPY3F 46GcKpQ/3ZTLtgJXk67oIlX64A4d5AYcSO2h0= 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=kvwIVbU5KGFWruGuiqkp9UOjjNlZ2MBp/MSyyd+xxjLA8PUgghjpL57KMa9hLjUG8v y+JgdbRgs4rErPaOGpz2jxX/tU6PT0drcBoTbHdXT/D02/kVMQ2h9P59QLWyocP3cJZc qPswdDrv4FZZzqPhWlLfUcVuyEV7c+4zCdKKE= Received: by 10.86.4.14 with SMTP id 14mr244174fgd.8.1237731551053; Sun, 22 Mar 2009 07:19:11 -0700 (PDT) Received: from ?192.168.1.25? (252.80.3.213.cust.bluewin.ch [213.3.80.252]) by mx.google.com with ESMTPS id 4sm1820210fgg.10.2009.03.22.07.19.10 (version=SSLv3 cipher=RC4-MD5); Sun, 22 Mar 2009 07:19:10 -0700 (PDT) Message-ID: <49C648DD.1020607@gmail.com> Date: Sun, 22 Mar 2009 15:19:09 +0100 From: phcoder User-Agent: Thunderbird 2.0.0.21 (X11/20090318) MIME-Version: 1.0 To: The development of GRUB 2 References: <49C63395.9090304@gmail.com> <200903222212.34194.okuji@enbug.org> <49C63D70.5020908@gmail.com> <200903222301.41688.okuji@enbug.org> In-Reply-To: <200903222301.41688.okuji@enbug.org> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.6 (newer, 2) Subject: Re: Move loader.c out of the kernel 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: Sun, 22 Mar 2009 14:19:19 -0000 Yoshinori K. Okuji wrote: > On Sunday 22 March 2009 22:30:24 phcoder wrote: >> Yoshinori K. Okuji wrote: >>> On Sunday 22 March 2009 22:06:36 phcoder wrote: >>>> Yoshinori K. Okuji wrote: >>>>> On Sunday 22 March 2009 21:48:21 phcoder wrote: >>>>>> Hello. Now when boot command isn't in kernel anymore I don't see why >>>>>> loader.c stays in kernel. Here is the patch to move it to boot.mod >>>>> This is not useful in reality, because the loader interface needs to be >>>>> pre-loaded into core.img anyway. >>>> Why? I successfully tested core.img with just pc fat and biosdisk >>>> modules integrated. It loads boot.mod just fine and boots linux and >>>> multiboot with no problem >>> Try the rescue mode with no extra module loaded. If the core.img does not >>> have any loader, it is useless. >> If it's unable to read FS then it can't boot much anyway. If it's it can >> load modules from its own partition. The only use I see is when grub >> partition is corrupted but OS one is intact and you already have FS >> driver for root in grub2. >> Alternatively commands/boot.c can be a part of minicmd > > "cannot load any more module" != "cannot read the filesystem" > > The most typical case is where the user has failed in installing GRUB > correctly; in this case, the user can still reset the prefix, and load > normal.mod manually. But, surprisingly, some users accidentally remove > modules. Indeed, I have heard many times this kind of "bug reports" in GRUB > Legacy. In this case, the only way is to boot an OS somehow and re-install > GRUB. Well if user damages grub2 then we can't do much. He can also accidently rewrite mbr or first track (some non-booting-realted software does it on purpose). For failsafe solution only cd is a viable alternative grub-install already handles the correct installation of grub2. Additionally if user has "accidently" deleted modules chances are he used grub-install or some wrapper around it. But grub-install doesn't put any loader modules to core.img. > > Regards, > Okuji > > > _______________________________________________ > Grub-devel mailing list > Grub-devel@gnu.org > http://lists.gnu.org/mailman/listinfo/grub-devel -- Regards Vladimir 'phcoder' Serbinenko