The eclass currently correctly remounts /boot to rw or mounts /boot pre-install or pre-rm, however, it leaves /boot like this when done merging. Ideally /boot mount options should be returned exactly the way it was found before tampering with it.
should be all set now. it might not recover 100% on an emerge of an already installed package since the post funcs arent in the emerged package's env, but it should pick up after that. http://sources.gentoo.org/eclass/mount-boot.eclass?r1=1.17&r2=1.18
Looks good thanks!
Hi, Afraid it remounts back to ro too soon, and also in cases where /boot was NOT mounted ro to begin with. We've just set up a chroot where /mnt/gentoo/boot was mounted rw, chroot, emerge -av grub-static resulted in: * * Automatically remounting /boot as ro * >>> Original instance of package unmerged safely. mv: cannot move `//boot/grub/stage2' to `//boot/grub/stage2.old': Read-only file system * *** IMPORTANT NOTE: you must run grub and install * the new version's stage1 to your MBR. Until you do, * stage1 and stage2 will still be the old version, but * later stages will be the new version, which could * cause problems such as an unbootable system. * This means you must use either grub-install or perform * root/setup manually! For more help, see the handbook: * http://www.gentoo.org/doc/en/handbook/handbook-amd64.xml?part=1&chap=10#grub-install-auto * Copying files from /lib/grub, /usr/lib/grub and /usr/share/grub to //boot/grub However, this may have been caused by an incorrect /etc/mtab entry indicating that /boot was mounted ro. However, in the case where we're in a live system with an actual ro /boot the above still happens. It would seem that the remounting back to ro (or unmounting) happens somewhere between src_install and pkg_postinstall. My suggestion would be to postpone this till after pkg_postinstall as this should resolve the issue we're experiencing currently. It should be as simple as renaming the function on line 104 of the eclass from mount-boot_pkg_postinst to whatever is the correct name. Please let me know if this should be considered a new bug or if it's OK to leave it here.
that is a bug in the grub ebuild. in the future, open a new bug. http://sources.gentoo.org/sys-boot/grub/grub-0.97-r8.ebuild?r1=1.2&r2=1.3 http://sources.gentoo.org/sys-boot/grub/grub-0.97-r9.ebuild?r1=1.6&r2=1.7 http://sources.gentoo.org/sys-boot/grub/grub-0.97-r10.ebuild?r1=1.8&r2=1.9 http://sources.gentoo.org/sys-boot/grub/grub-1.98.ebuild?r1=1.6&r2=1.7 http://sources.gentoo.org/sys-boot/grub/grub-9999.ebuild?r1=1.27&r2=1.28