From: ludo@gnu.org (Ludovic Courtès)
To: Gennadii Kondratiev <gennadii.kondratiev@gmail.com>
Cc: 25248@debbugs.gnu.org
Subject: bug#25248: please, include Legacy Grub in your distro
Date: Thu, 29 Dec 2016 22:58:04 +0100 [thread overview]
Message-ID: <87pokae6tv.fsf@gnu.org> (raw)
In-Reply-To: <CAEQpGjJKpK6F5xNDbJgTJNjMDu=Nri5oSf=+M-YEQonJo-HXGQ@mail.gmail.com> (Gennadii Kondratiev's message of "Thu, 22 Dec 2016 18:57:17 +0300")
Hello!
Gennadii Kondratiev <gennadii.kondratiev@gmail.com> skribis:
> May I ask you and everybody in GNU organization to again include Legacy
> Grub as a normal package in GuixSD and in everything? The reason is that it
> is just terrible to install the system and after not to have access to it
> or invent something how to boot it. Grub2 is invalide. For what anybody
> does need such an entity which cannot install itself on a arbitrary
> prtition? Of course, people use different operating systems, which are on
> different partitions. I always install grub on the root partition. But
> Grub2 does not work, because you specially cut its ability.
Could you explain how you installed GuixSD and what exactly goes wrong
with GRUB (error messages, etc.)?
> !!!Please, include Legacy Grub in GuixSD!!!
GRUB 1.x is unmaintained AFAIK, and it’s incompatible and has a reduced
feature set. It’s unlikely that we’ll add it to GuixSD.
However, if you have troubles with GuixSD and GRUB 2.x, then we should
certainly fix them, either in GuixSD or in GRUB!
Thanks,
Ludo’.
next prev parent reply other threads:[~2016-12-29 21:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-22 15:57 bug#25248: please, include Legacy Grub in your distro Gennadii Kondratiev
2016-12-29 21:58 ` Ludovic Courtès [this message]
2016-12-30 17:20 ` bug#25248: Merry Christmas and Happy New Year! GRUB1 and GRUB2 Gennadii Kondratiev
2016-12-31 19:53 ` Tomáš Čech
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87pokae6tv.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=25248@debbugs.gnu.org \
--cc=gennadii.kondratiev@gmail.com \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).