From: Christian Franke <Christian.Franke@t-online.de>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: [PATCH] ntldr support
Date: Sat, 08 Aug 2009 23:57:48 +0200 [thread overview]
Message-ID: <4A7DF4DC.5010106@t-online.de> (raw)
In-Reply-To: <d7ead6de0908080455u49f7a03dt369727298e6db695@mail.gmail.com>
Vladimir 'phcoder' Serbinenko wrote:
>> About the command, i think that it will be simpler for the user if we have
>> only one command: chainloader (like in grub4dos) that will try to detect the
>> type of the bootloader. This is only my personal opinion.
>>
> I don't agree with this. chainloader and ntldr don't share the same
> syntax: chainloader expects a bootsector whereas ntldr expects an
> ntldr ot bootmgr file. GRUB2 is done to break with bad design
> decisions of GRUB1 one of them being "kernel" command. GRUB4DOS
> follows GRUB1 on this subject.
>
I agree.
It probably would make sense that the 'ntldr' command does simple
signature checks and fail on unknown files unless '--force' is specified.
--
Regards,
Christian Franke
next prev parent reply other threads:[~2009-08-08 21:58 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-02 23:24 [PATCH] ntldr support Robert Millan
2009-08-04 18:36 ` Christian Franke
2009-08-04 19:27 ` Robert Millan
2009-08-04 20:09 ` Vladimir 'phcoder' Serbinenko
2009-08-05 5:35 ` Christian Franke
2009-08-07 10:58 ` Robert Millan
2009-08-07 11:17 ` Michal Suchanek
2009-08-07 11:43 ` Robert Millan
2009-08-07 22:55 ` Michal Suchanek
2009-08-08 21:44 ` Christian Franke
2009-08-08 11:45 ` Yves Blusseau
2009-08-08 11:55 ` Vladimir 'phcoder' Serbinenko
2009-08-08 21:57 ` Christian Franke [this message]
2009-08-10 11:52 ` Robert Millan
2009-08-10 18:57 ` Christian Franke
2009-08-10 19:55 ` Vladimir 'phcoder' Serbinenko
2009-08-10 21:00 ` Christian Franke
-- strict thread matches above, loose matches on Subject: below --
2009-10-25 23:28 Nando
2009-10-26 1:05 ` Robert Millan
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=4A7DF4DC.5010106@t-online.de \
--to=christian.franke@t-online.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.