From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1KaxhO-0005GQ-6d for mharc-grub-devel@gnu.org; Wed, 03 Sep 2008 15:07:26 -0400 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1KaxhN-0005Fd-Ce for grub-devel@gnu.org; Wed, 03 Sep 2008 15:07:25 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1KaxhL-0005FQ-K0 for grub-devel@gnu.org; Wed, 03 Sep 2008 15:07:24 -0400 Received: from [199.232.76.173] (port=53723 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1KaxhL-0005FL-FR for grub-devel@gnu.org; Wed, 03 Sep 2008 15:07:23 -0400 Received: from mta-out.inet.fi ([195.156.147.13]:43104 helo=jenni1.inet.fi) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1KaxhK-0000yj-Nl for grub-devel@gnu.org; Wed, 03 Sep 2008 15:07:23 -0400 Received: from [127.0.0.1] (88.193.32.97) by jenni1.inet.fi (8.5.014) id 488F153401A9173C for grub-devel@gnu.org; Wed, 3 Sep 2008 22:07:22 +0300 Message-ID: <48BEE06D.20202@nic.fi> Date: Wed, 03 Sep 2008 22:07:25 +0300 From: =?ISO-8859-1?Q?Vesa_J=E4=E4skel=E4inen?= User-Agent: Thunderbird 2.0.0.16 (Windows/20080708) MIME-Version: 1.0 To: The development of GRUB 2 References: <48BE5DE9.4090302@gmail.com> <20080903103654.GC29762@thorin> <48BE838E.9090204@gmail.com> <48BEC078.7030006@nic.fi> <48BEC6AD.5040305@gmail.com> <48BECE1A.1070406@nic.fi> <48BED931.2010208@gmail.com> In-Reply-To: <48BED931.2010208@gmail.com> X-Enigmail-Version: 0.95.7 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: Quoted-Printable X-detected-kernel: by monty-python.gnu.org: Linux 2.6 (newer, 3) Subject: Re: [RFC] Boot parameters and geometrical stability 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: Wed, 03 Sep 2008 19:07:25 -0000 phcoder wrote: > Vesa J=E4=E4skel=E4inen wrote: >> That is a valid point. >> >> Would you prefer to use hardware path to device or what you had in min= d >> then? Because this is something that we can left for expert people. Mo= st >> common problem is that user plugs in new drive to system and >> bios/hardware order gets changed or something like that, and that >> renders system unbootable. UUID is perfect solution for that case. >> > Yes it is, but in my opinion price is too high (shame ubuntu uses this > solution). It's somewhat similar to some solutions found in windows whe= n > for user convenience they open a big gate for the hackers (e.g. all > users by default are administrators in winxp) Well... That is your opinion. I acknowledge that it opens another door for local hacker. But if you are able to do that, then you can do some other actions that are much more fatal... But the gain can still supersede the security need. Its kinda same thing that you are required to change your password monthly. People start putting those on stickers and then the game is lost anyway. >> Possibilites are there, but basically they are limited to something li= ke: >> >> (ata0) (pci-X-Y-Z:ata0) (usb-X-Y:scsi0) (pci-X-Y-Z:scsi0) >> >> I do not know if those all would be valid, but I hope you get the idea= =2E >=20 > Yes. This is a solution found in grub legacy and I think it's a good on= e. We already have (hdX) and (ataY) in GRUB 2. Especially (hdX) has lots of problems that this UUID was used to workaround.