Description of problem: Documentation of boot floppy creation is incorrect Version-Release number of selected component (if applicable): 1.99 How reproducible: N/A Steps to Reproduce: 1. info grub2 Installation "Installing GRUB" 2. 3. Actual results: [...] The typical usage is that you create a GRUB boot floppy with a filesystem. Here is an example: # mke2fs /dev/fd0 # mount -t ext2 /dev/fd0 /mnt # mkdir /mnt/boot # grub2-install --boot-directory=/mnt/boot /dev/fd0 # umount /mnt Expected results: Some correct example. (I don't know what that would be.) Additional info: 0) This bug is filed assuming people working on the Fedora side also do some upstream work. If not, I'll be glad to report this upstream. 1) To be complete, this is what I got while trying the example. (Not having an actual floppy, I loop mounted an image. I don't expect that to be relevant for this bug.) $ dd if=/dev/zero bs=1024 count=2880 of=ext2.img 2880+0 records in 2880+0 records out 2949120 bytes (2.9 MB) copied, 0.0160954 s, 183 MB/s $ mke2fs ext2.img mke2fs 1.41.14 (22-Dec-2010) ext2.img is not a block special device. Proceed anyway? (y,n) y Filesystem label= OS type: Linux Block size=1024 (log=0) Fragment size=1024 (log=0) Stride=0 blocks, Stripe width=0 blocks 360 inodes, 2880 blocks 144 blocks (5.00%) reserved for the super user First data block=1 Maximum filesystem blocks=3145728 1 block group 8192 blocks per group, 8192 fragments per group 360 inodes per group Writing inode tables: done Writing superblocks and filesystem accounting information: done This filesystem will be automatically checked every 26 mounts or 180 days, whichever comes first. Use tune2fs -c or -i to override. $ sudo mount -o loop ext2.img /mnt $ mkdir /mnt/boot $ sudo grub2-install --boot-directory=/mnt/boot /dev/loop0 /sbin/grub2-setup: warn: Attempting to install GRUB to a partitionless disk or to a partition. This is a BAD idea.. /sbin/grub2-setup: warn: Embedding is not possible. GRUB can only be installed in this setup by using blocklists. However, blocklists are UNRELIABLE and their use is discouraged.. /sbin/grub2-setup: error: will not proceed with blocklists.
(In reply to comment #0) > 0) This bug is filed assuming people working on the Fedora side also do some > upstream work. If not, I'll be glad to report this upstream. That is hardly the case, so it would be better if you could report it upstream. Upstream is aware that their documentation needs a massive update, so they would probably appreciate a patch more than a bug report ;-)
This message is a reminder that Fedora 16 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 16. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '16'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 16's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 16 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged to click on "Clone This Bug" and open it against that version of Fedora. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.