On Dec 27, 2012 12:58 PM, "Chris Murphy" <lists@xxxxxxxxxxxxxxxxx> wrote:
>
>
> On Dec 26, 2012, at 7:53 AM, Ben Cotton <bcotton@xxxxxxxxxxxxxxxxx> wrote:
>
> > Nevermind. I seem to have missed the link in your first message.
>
>
> There's feedback in the bug that points out there are user specific considerations that change the instructions, example given is boot on a separate partition.
>
> I may be that a bulk of this belongs in the Installation Guide, and the release note just points out that installing GRUB to a partition is not supported, and where to get more information for recommended alternatives. I suspect release notes are to be more concise, rather than have full blown how-to guides in them.
>
> e.g. If boot is on a separate partition, there's a change in prefix; if boot in on LVM, it's different yet again.
>
> Also there's some concern about 'configfile' from a sufficiently old GRUB2 pre-release (which had been around for years before this summer's final release of 2.00), in which the early GRUB2 may not (fully) understand the present Fedora 18 GRUB2-2.00 based grub.cfg. There have been many syntax changes in grub.cfg which have at least affected grubby's ability to alter the grub.cfg, depending on the version of grub2-mkconfig that created it. So in this case, an entry in the first instance of GRUB2 using 'multiboot $prefix/i386-pc/core.img' can be used to load Fedora's GRUB.
>
> Arguably users are hurting themselves by running such old pre-release versions of GRUB2, and in my opinion should be encouraged to upgrade GRUB from within their primary distro, or make Fedora their primary distro.
>
> In comparison, the commands to create the core.img and grub.cfg are trivial to document than how to use them (per above). Nevertheless, I'm still hopeful that this NTH bug will take care of the creation part.
> https://bugzilla.redhat.com/show_bug.cgi?id=886502
>
>
> Chris Murphy
>
> --
I've been pondering this topic , and other conversations from various lists on the state of anaconda. A lot of work has gone into the Installation Guide for this release, and I agree that it is probably the best place for more specific details.
For the Release Notes, I'm hesitant to delve into the various affected use cases; a blurb might be insufficient, a couple paragraphs too much, and including some situations alludes to the omission of others. How do we all feel about a note along the lines of "Not all features are available from the GUI, but advanced needs can be met with a kickstart installation or through post-install configuration" with links to appropriate documentation?
The concern about should certainly be in the 'common bugs' wiki page, if not the release notes. I'll watch the bug.
-- docs mailing list docs@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/docs
