On 06/30/2012 05:50 AM, Dale wrote:
Thanks. Now more questions. I have read about this a few times but
never quite figured it out. I copy the bzImage and name it bzImage-*
because that is what it is named when I type make etc to build a
kernel. Is there a difference between bzImage and vmlinux? If it is,
is it safe to rename it like that or will it break something? If I
need a vmlinux kernel instead of a bzImage, where is that thing? I
have looked and I don't have one on mine here. Maybe I am missing
something. Google didn't find me anything either.
The bzImage is a vmlinuz (or vmlinuz) image, and is what grub2 expects
to use with a "linux" kernel definition.
I usually copy the bzImage to a file named "gentoo.XYZ" where the XYZ is
the kernel version number. I'm not sure if
grub-mkconfig is yet smart enough to figure it out completely, but I've
been using grub2 with my gentoo partitions for a while.
Certainly, grub-mkconfig in fedora recognizes the gentoo disk properly
as another linux installation (via the os-prober) and
builds menuentries for them. It may just be reading the grub2/grub.cfg
file I wrote.
One thing is certain, grub2 doesn't have to have all the scripting and
rigamarole that fedora and GNU put in via the grub-mkconfig
command, a simple config file will work as well. GNU has grub2 in the
RC1 phase right now and I've built it under fedora and gentoo
and use it. I've gone from using a grub2 cdrom boot to using the BIOS
boot menu device select to control whether I'm going into
Linux or Win7 (Win7 is on the default device and grub2 for fedora and
gentoo are on other discs.)
I'm using a shared /home partition with slightly different uids for each
system, but a common "username". Each uid homedir
contains native dotfiles for a variety of services and some symlinks to
a common set of {Documents, Downloads,Public,Pictures,
and public_html} directories.
Grub2 isn't that hard to do, it's just /different/
