It does actually: Ive suffered a lost/corruted (ext2/3) boot partition a few times when its been left mounted. Dont do that anymore! A simple script can handle the build process including mounting/unmounting /boot, without the complexities of genkernel.
Also I stopped using genkernel some time back when it suffered from a number of problems handling odd configurations, overwrote older configs, took too long to fault find when it (often) went wrong and the built kernel seemed a poor performer in comparison with a hand built one. Overall, genkernel is a great solution for the beginner (when it worked, which it often didnt for me), but eventually you need to get your hands dirty in any case. Many of the problems have probably been fixed, but I am in no hurry to go back just in case. BillK On Mon, 2005-04-11 at 18:18 -0400, Eric S. Johansson wrote: > Bastian Balthazar Bux wrote: > > Matthew Cline wrote: > > > >>> I recommend using genkernel for creating a kernel. You still have to > >>> deal with configuring yourself, but then Gentoo deals with the compile > >>> and moving the kernel around and such. > >> > >> > >> > >> What's wrong with make && make modules_install && make install? > > > > > > probably that you forget 50% of the times the > > # mount /boot > > ;) (I've started to mount it read only so at least an error came up) > > I always leave it mounted since it makes little real difference security > wise. seriously, what does it protects you against when a compromise > can probably also mount it then unmount it again as a courtesy > > -- William Kenworthy <[EMAIL PROTECTED]> Home! -- gentoo-user@gentoo.org mailing list
