From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id C70A41384C0 for ; Sat, 29 Aug 2015 16:58:07 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 4AB5214283; Sat, 29 Aug 2015 16:57:49 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 2246E14228 for ; Sat, 29 Aug 2015 16:57:48 +0000 (UTC) Received: from mail-io0-f170.google.com (mail-io0-f170.google.com [209.85.223.170]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: floppym) by smtp.gentoo.org (Postfix) with ESMTPSA id 4A9B43408EC for ; Sat, 29 Aug 2015 16:57:46 +0000 (UTC) Received: by iofe124 with SMTP id e124so56540416iof.1 for ; Sat, 29 Aug 2015 09:57:44 -0700 (PDT) X-Received: by 10.107.38.67 with SMTP id m64mr992724iom.89.1440867464236; Sat, 29 Aug 2015 09:57:44 -0700 (PDT) Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 Received: by 10.107.17.95 with HTTP; Sat, 29 Aug 2015 09:57:24 -0700 (PDT) In-Reply-To: <55E1DB22.50608@comcast.net> References: <55DE3D41.1050301@comcast.net> <55E1DB22.50608@comcast.net> From: Mike Gilbert Date: Sat, 29 Aug 2015 12:57:24 -0400 Message-ID: Subject: Re: [gentoo-user] Re: Grub1: Cant ? Re: keeping grub 1 To: gentoo-user@lists.gentoo.org Content-Type: text/plain; charset=UTF-8 X-Archives-Salt: eebf3d82-f595-4cef-afad-6ac6b0fb3fbf X-Archives-Hash: d154670882fda4eef42997ba735eddb9 On Sat, Aug 29, 2015 at 12:17 PM, Michel Catudal wrote: > You have to be able to boot the os that grub is installed on to be able to > fix booting issues. If the OS that has control of grub2 is wacked you are > screwed. > At least with a bootloader that independant of any operating system and with > a nice graphic interface it is a piece of cake to fix things since you do > not ever lose your bootloader unless you let grub write on the MBR or on > your bootloader partition. > > I know that you can boot on grub if it is not wiped but the interface is not > friendly at all and if you do not remember the syntax you are screwed. Until > grub becomes a nice real bootloader with a friendly user interface it cannot > be allowed to be the sole controller of booting. The grub config syntax is not really that bad; the main issue is that grub-mkconfig generates a very complex config file to try and cover a lot of possible systems. grub is pretty much designed to be able to boot any OS you have installed on any filesystem. That flexibility carries with it a level of complexity as well. If you don't need that flexibility, a simpler boot loader is always an option for you. If you want an "OS-independent" boot loader, the syslinux family of boot loaders might be a good choice for you. Or keep using grub legacy. Just don't expect either of them to be able to boot Linux from ZFS, or ext4 on lvm on luks. That's where grub2 comes in handy.