grub-devel.gnu.org archive mirror
 help / color / mirror / Atom feed
From: "Vladimir 'φ-coder/phcoder' Serbinenko" <phcoder@gmail.com>
To: grub-devel@gnu.org
Subject: Re: Add prefix option to grub-mkconfig
Date: Wed, 26 Oct 2011 23:04:00 +0200	[thread overview]
Message-ID: <4EA875C0.3010803@gmail.com> (raw)
In-Reply-To: <CAMPnHXyks35BPNSbBMjE8Y=bknGOO04mE1i=iLJPRtM2JsUs4A@mail.gmail.com>

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

On 26.10.2011 22:54, Keshav P R wrote:
> On Thu, Oct 27, 2011 at 02:18, Seth Goldberg <seth.goldberg@oracle.com
> <mailto:seth.goldberg@oracle.com>> wrote:
>
>     Hi,
>
>      Personally, I'd love to see boot-directory go away also -- I
>     think you should be able to specify the exact directory you want
>     without worrying about /grub being appended.  Same goes for mkconfig.
>
>      --S
>
>
> Yes, that would be best and gives direct control to the user. For now
> GRUB_PREFIX denotes that final dir (atleast in the scripts).
>
Ok, I open directory you specifiec without thinking too much and spill
loads of files in it. Happy sorting.
> - Keshav
>  
>
>
>     Quoting Keshav P R, who wrote the following on Thu, 27 Oct 2011:
>
>         Hi all,
>               As discussed in #grub irc, I think going the
>         --boot-directory way as
>         phcoder suggested will lead to unnecessary complexity. I would
>         prefer
>         directly mentioning the path to grub_prefix dir, as in case of
>         uefi installs
>         the prefix dir could be anything (/efi/grub, /efi/grub2,
>         /efi/grub_custom,
>         /efi/redhat, /efi/ubuntu etc.). Using --boot-directory in such
>         a case also
>         requires --bootloader-id etc. to be provided.
>              Proper GRUB_PREFIX is required for video.lst and
>         locale_dir setting
>         in grub.cfg. The patch with --prefix option is at
>         http://pastie.org/2763921. Please give your views.
>
>         Regards.
>
>         Keshav
>
>
>     _______________________________________________
>     Grub-devel mailing list
>     Grub-devel@gnu.org <mailto:Grub-devel@gnu.org>
>     https://lists.gnu.org/mailman/listinfo/grub-devel
>
>
>
> _______________________________________________
> Grub-devel mailing list
> Grub-devel@gnu.org
> https://lists.gnu.org/mailman/listinfo/grub-devel


-- 
Regards
Vladimir 'φ-coder/phcoder' Serbinenko



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 294 bytes --]

  reply	other threads:[~2011-10-26 21:04 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-22 18:02 Add prefix option to grub-mkconfig KESHAV P.R.
2011-09-16  6:17 ` KESHAV P.R.
2011-09-16 17:18   ` Seth Goldberg
2011-10-13 21:29 ` Jamie Kitson
2011-10-26 20:44   ` Keshav P R
2011-10-26 20:48     ` Seth Goldberg
2011-10-26 20:54       ` Keshav P R
2011-10-26 21:04         ` Vladimir 'φ-coder/phcoder' Serbinenko [this message]
2011-10-26 21:07           ` Seth Goldberg
2011-10-26 21:14             ` Vladimir 'φ-coder/phcoder' Serbinenko
2011-10-26 21:22               ` Seth Goldberg
2011-10-26 21:42                 ` Vladimir 'φ-coder/phcoder' Serbinenko
2011-10-26 22:23                   ` Seth Goldberg
2011-11-22  9:21                     ` Keshav P R
2011-11-25 13:26                       ` Vladimir 'φ-coder/phcoder' Serbinenko

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=4EA875C0.3010803@gmail.com \
    --to=phcoder@gmail.com \
    --cc=grub-devel@gnu.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;
as well as URLs for NNTP newsgroup(s).