Maxim Kammerer posted on Tue, 20 Mar 2012 21:31:53 +0200 as excerpted: > On Tue, Mar 20, 2012 at 18:07, Mike Gilbert <flop...@gentoo.org> wrote: >> So, my question to the community: what level of documentation do we >> want to put in the handbook? > > I think that the EFI usecase should be well-documented, since EFI is the > reason that many users migrate to GRUB 2.
Currently, you're right. But consider that we're talking about unmasking grub2 to ~arch and ultimately to stable, at which point it should be in the handbook and all x86 and amd64 users will be getting it, that won't remain the case forever. >> Is there any other issue with grub:2 that would keep me from unmasking >> (adding keywords) on x86 and amd64? I plan on waiting for the 2.00 >> release. > > Note that whereas 1.99 searches for modules in $prefix, 2.00 searches > for them in $prefix/<arch>. FWIW, the 2.00 betas haven't been entirely smooth for me. beta0 was fine. beta1 would load to grub but would reboot when I tried to boot a kernel, so I masked it. beta2 is getting there, but there's still some problems with various interactive commands. IIRC it was help cat that triggered a reboot here, while cat --help (or was it cat -h?) works. But with one of the other commands I tried, it was the reverse, help <command worked for it, but <command> --help did nothing (at least it didn't trigger a reboot as help cat did). Assuming those sorts of issues are gone by 2.00 release, it should be a reasonable target. But I'd definitely recommend thorough testing both at the maintainer level, and with an elog urging users who have manually unmasked it to file any remaining bugs ASAP, before it's unmasked to ~arch. Talking about which, should I actively pursue bug filing on it yet? With gentoo, upstream, or both? If you're actively wanting those bugs now, please do put an elog to that effect in the ebuild, and I'll start being particular about stuff like help cat working, and filing bugs if it doesn't! -- Duncan - List replies preferred. No HTML msgs. "Every nonfree program has a lord, a master -- and if you use the program, he is your master." Richard Stallman
