public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Neil Bothwick <neil@digimed.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: Switching from grub to grub2 - WAS Re: [gentoo-user] fdisk warnings during install; questions
Date: Sat, 11 May 2013 17:52:19 +0100	[thread overview]
Message-ID: <20130511175219.2afe5bc1@digimed.co.uk> (raw)
In-Reply-To: <F6B5501B-4F05-4B47-A1F1-6C3CC23573D9@stellar.eclipse.co.uk>

[-- Attachment #1: Type: text/plain, Size: 1229 bytes --]

On Sat, 11 May 2013 12:39:41 +0100, Stroller wrote:

> >> So, how was  the switch? Uneventful? The more I read, and once I
> >> learned you could still use a monolithic config file, the less this
> >> looks like a big deal...  
> > 
> > STILL use a monolithic config file? GRUB2 has to use a monolithic
> > config file, usually /boot/grub2/grub.cfg. grub-mkconfig is not a
> > bootloader, just an easy way of managing that monolithic
> > configuration file.  
> 
> You seem to have take it as a criticism, but I read previous message as
> approving of monolithic config files.
> 
> "grub2 looks ok, because it still uses a monolithic config file"

I read it different because of the use of the word "could". It is not an
option with GRUB2, it is a requirement. The format and name of the file
have changed, but it is still a single file. The only optional aspect is
how you create that file. With the old GRUB you have to write it by hand,
now you have a second option.

There seems a perception that you have to use the files in /etc/grub.d
and /etc/default, but this a absolutely not the case, and never has been. 


-- 
Neil Bothwick

If you got the words it does not mean you got the knowledge.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

  reply	other threads:[~2013-05-11 16:52 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-10  1:11 [gentoo-user] fdisk warnings during install; questions Walter Dnes
2013-05-10  7:52 ` Michael Hampicke
2013-05-10  8:47   ` Neil Bothwick
2013-05-10  9:44     ` Alan McKinnon
2013-05-10 10:00       ` Neil Bothwick
2013-05-10 10:55         ` Alan McKinnon
2013-05-10 11:04           ` Neil Bothwick
2013-05-10 11:09           ` Dale
2013-05-10 11:40             ` Neil Bothwick
2013-05-10 12:10               ` Dale
2013-05-10 12:23                 ` Neil Bothwick
2013-05-10 13:22                   ` Dale
2013-05-10 19:40                     ` Neil Bothwick
2013-05-10 13:33             ` Switching from grub to grub2 - WAS " Tanstaafl
2013-05-10 19:09               ` Dale
2013-05-11  0:04                 ` [gentoo-user] Re: Switching from grub to grub2 - WAS " walt
2013-05-10 19:42               ` Switching from grub to grub2 - WAS Re: [gentoo-user] " Neil Bothwick
2013-05-11 11:39                 ` Stroller
2013-05-11 16:52                   ` Neil Bothwick [this message]
2013-05-10 15:54           ` J. Roeleveld
2013-05-10 13:31         ` Tanstaafl
2013-05-10 15:54         ` Walter Dnes
2013-05-10 19:36           ` Neil Bothwick
2013-05-10 15:40       ` Walter Dnes
2013-05-10 11:36     ` Thanasis
2013-05-10 11:41       ` Wang Xuerui
2013-05-10 11:41       ` Neil Bothwick
2013-05-10 14:57       ` Bruce Hill
2013-05-10 10:26 ` pk
2013-05-10 16:28 ` Walter Dnes
2013-05-10 22:06   ` Mick

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20130511175219.2afe5bc1@digimed.co.uk \
    --to=neil@digimed.co.uk \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox