From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1Mz8LR-0006Oi-Lw for mharc-grub-devel@gnu.org; Sat, 17 Oct 2009 08:25:13 -0400 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Mz8LM-0006MJ-Nw for grub-devel@gnu.org; Sat, 17 Oct 2009 08:25:09 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Mz8LH-0006IY-O6 for grub-devel@gnu.org; Sat, 17 Oct 2009 08:25:08 -0400 Received: from [199.232.76.173] (port=59321 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Mz8LH-0006IL-4W for grub-devel@gnu.org; Sat, 17 Oct 2009 08:25:03 -0400 Received: from mailhub.sw.ru ([195.214.232.25]:11059 helo=relay.sw.ru) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1Mz8LG-0005hk-Ie for grub-devel@gnu.org; Sat, 17 Oct 2009 08:25:02 -0400 Received: from [10.30.3.27] ([10.30.3.27]) by relay.sw.ru (8.13.4/8.13.4) with ESMTP id n9HCOrPZ021283 for ; Sat, 17 Oct 2009 16:24:57 +0400 (MSD) Message-ID: <4AD9B795.6000201@parallels.com> Date: Sat, 17 Oct 2009 16:24:53 +0400 From: Vasily Averin User-Agent: Thunderbird 1.5.0.10 (X11/20060911) MIME-Version: 1.0 To: grub-devel@gnu.org X-Enigmail-Version: 0.94.2.0 Content-Type: multipart/mixed; boundary="------------060200080606060208040908" X-detected-operating-system: by monty-python.gnu.org: OpenBSD 3.0-3.9 Subject: [patch] incorrect root device while /dev/ on tmpfs 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, 17 Oct 2009 12:25:10 -0000 This is a multi-part message in MIME format. --------------060200080606060208040908 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit While /dev mounted as tmpfs it does not contain /dev/disk/by-uuid directory, 10_linux script did not check it properly and do not set root device via UUID. Therefore following kernel boot can fail (incorrect root device) if device names was changed. Attached path fixes this issue. Please review and commit it thank you, Vasily Averin --------------060200080606060208040908 Content-Type: text/plain; name="grub2-tmpdevuuid.patch" Content-Transfer-Encoding: base64 Content-Disposition: inline; filename="grub2-tmpdevuuid.patch" ZGlmZiAtdXAgLi91dGlsL2dydWIuZC8xMF9saW51eC5pbi50bXBkZXZ1dWlkIC4vdXRpbC9n cnViLmQvMTBfbGludXguaW4KLS0tIC4vdXRpbC9ncnViLmQvMTBfbGludXguaW4udG1wZGV2 dXVpZAkyMDA5LTA4LTI5IDIwOjA1OjA2LjAwMDAwMDAwMCArMDQwMAorKysgLi91dGlsL2dy dWIuZC8xMF9saW51eC5pbgkyMDA5LTA5LTAzIDExOjA3OjM0LjAwMDAwMDAwMCArMDQwMApA QCAtMzYsNyArMzYsNyBAQCBjYXNlICR7R1JVQl9ERVZJQ0V9IGluCiBlc2FjCiAKIGlmIFsg Ingke0dSVUJfREVWSUNFX1VVSUR9IiA9ICJ4IiBdIHx8IFsgIngke0dSVUJfRElTQUJMRV9M SU5VWF9VVUlEfSIgPSAieHRydWUiIF0gXAotICAgIHx8ICEgdGVzdCAtZSAiL2Rldi9kaXNr L2J5LXV1aWQvJHtHUlVCX0RFVklDRV9VVUlEfSIgOyB0aGVuCisgICAgfHwgKCB0ZXN0IC1k IC9kZXYvZGlzay9ieS11dWlkICAmJiAhIHRlc3QgLWUgIi9kZXYvZGlzay9ieS11dWlkLyR7 R1JVQl9ERVZJQ0VfVVVJRH0iKSA7IHRoZW4KICAgTElOVVhfUk9PVF9ERVZJQ0U9JHtHUlVC X0RFVklDRX0KIGVsc2UKICAgTElOVVhfUk9PVF9ERVZJQ0U9VVVJRD0ke0dSVUJfREVWSUNF X1VVSUR9Cg== --------------060200080606060208040908--