I find it very, very bad idea to automatically mount partitions during any emerge. And the actual behavior prevends any scripted or chrooted installation where /boot could not be mounted. I don't think that was a good idea. Regards, Alexander
how do you propose we go about installing a boot loader properly then ? installing onto the root partition doesnt help at all if the boot partition is empty ... and as for 'preventing any scripted or chrooted installation', sounds more like the script is incomplete ...
nobody else in the community has a problem with this. its designed to 'save users from themselves' quite frankly. there is regexes in the mount-boot.eclass that work with the gentoo linux default fstab, so that it doesnt error out. what is the problem you're having?
It should read nobody else has written a bug report. I know some people who are finding that a bad behaviour too. Just see bug #527. If I install anything, I don't want that the installation routine mounts anything, starts any service, or adds any service automatically to my startup (like vmware) without my explicit permission (during a flag in make.conf or something else). And I'm pretty sure, many others are thinking the same. Regards, Alexander
the auto-init script setup was fixed ... as well as with any other ebuild that did that. in the Gentoo policy we have defined 'no ebuild shall install an rcscript automatically' as for Bug 527, that is *very* outdated and *does not apply at all* to your current request and as for this being a 'bad idea', i havent seen a valid arguement yet ... and if 'many other ppl feel the same way', we havent heard it yet (almost 14000 bugs and thousands of e-mails on lists, no mention of this 'problem')
- Why need gentoo's grub an extra partition? - Who knows what is on the partition I called /boot in my fstab? - Why do I need a boot partition (and therefore at least two partitions) for gentoo? - Who's sure that my /boot is not an nfs mounted through a wireless line over a wireless phone which costs many dollars per minute? I could find some reasons more. ;) Regards, Alexander
- Why need gentoo's grub an extra partition? you dont ... if you dont define a /boot partition grub wont use it ... but it is suggested, that way if your root fs eats it, your kernel and such is on a sep partition ... plus its more flexible this way ... make a small /boot at the beginning of the drive and you're *way* under the old school 1024 boundary for booting ... - Who knows what is on the partition I called /boot in my fstab? well, who the hell puts anything *but* boot related materials into /boot ? if you dont want to use grub, dont emerge it - Why do I need a boot partition (and therefore at least two partitions) for gentoo? this is the same exact question as #1 and the same exact answer - Who's sure that my /boot is not an nfs mounted through a wireless line over a wireless phone which costs many dollars per minute? why the hell would you have a /boot mounted remotely ? that would *totally* defeat the purpose of a /boot partition ... and if it *really* was, well update grub on the remote box, why do you need the local copy - I could find some reasons more. ;) well you're gonna have to because you havent provided a single valid reason yet
Forget it, because I'm drifting more and more away from gentoo using my own rsync, which has the place for an additional own ebuild, I don't need gentoo's grub anymore.
if you provide a valid reason for why this should be changed then we'd be happy to modify the current system you can utilize the 'PORTDIR_OVERLAY' to maintain local copies of ebuilds (in this case grub) so that you dont have to maintain your own rsync
woodchip: any thoughts ? i may have been a little zealous in my responses ;)
