I was changing from lilo-22.8-r2 to grub-0.97-r12 on three of my amd64 gentoos. First I emerged grub and then I unmerged lilo When I did "emerge --unmerge lilo && emerge --depclean" and wanted to configure /boot/grub/grub.conf, I noticed that /boot was gone. I have only one x86 gentoo and this one did not have this behaviour. I've set the bug to "trivial" because I didn't have /boot mounted when I unmerged lilo so just creating the /boot folder and remounting was all I needed to do. If you need more information, don't hesitate to ask. Greetings, Edward Dorosz
I cannot confirm this. Hadn't you any .keep file in /boot ?
(In reply to comment #1) > I cannot confirm this. > Hadn't you any .keep file in /boot ? I just checked and there are 2 .keep files: .keep .keep_sys-boot_lilo-0 But only when my boot partition is mounted. /boot was never mounted when I unmerged lilo so there weren't any .keep files when unmerging.
Understand. So it removes the mountpoint. I can confirm.
I do not think that this is amd64-specific problem
well, you shouldn't be mounting paths, installing packages on top of them, and then unmounting & unmerging. that's a really bad idea in general. in this case with lilo, i don't think we need the `keepdir /boot`. we can let the pkg_postinst code run `mkdir -p /boot`.
I understand why it isn't a good idea. I've reread my first post and it wasn't very clear. How I explained it, it says: 1. mount /boot 2. emerge grub 3. unmount /boot 4. unmerge lilo But what I did was: 1. mount /boot 2. emerge grub 3. configure grub + grub-install 4. reboot to see if everything was OK 5. unmerge lilo After that, I wanted to continue configuring grub for the fancy eyecandy at boot but the mount point was gone. I didn't give thought to remounting /boot before unmerging lilo. That's why I didn't have the same problem on the x86. It was the last pc I changed and also the least important so I removed lilo immediately after installing grub without a reboot. Thank you all for your help. Greetings, Edward
*** This bug has been marked as a duplicate of bug 377427 ***