This is my first time around with Gentoo, and I am impressed. Never liking rpm, and ALWAYS frustrated with rpm/source disfunction, gentoo seems a dream. I'm building a gateway that will port forward according to service. This is the machine that has a first for me. I've just completed, with interuption and delay, most of the pre-reboot installation of gentoo. I am now at the point of writting grub, and in doing so, I sought to learn my EXACT kernel file description. So I went to /boot, looking there for kernel information (coming from a RedHat exposure...). I couldn't find any. Huh. But I did notice that within boot, I also had a boot directory. I don't remember that ever being there. A few recursions later, and I'm six deep into /boot. I still haven't found my kernel images, nor configured grub. But this behavior seems to be saying I'd best fdisk and try again. All the same, I've NEVER seen this in ANY OS, and I've worked with four of them. Hope you can help --- further still. The entirety of gentoo is freedom for me, and I am greatful. David Weeks Reproducible: Always Steps to Reproduce: 1.Install from the Universal CD, fdisking, mkfs-c-ing. 2.Erase contents and restart two times, including fsck. 3.Complete installation to the point of writting the grub configuration file, and then look for the kernel, and discover recursive /boot directories. Actual Results: Got really upset, and decided to file this report. Expected Results: Peace and harmony, or at least the presence of the newly compiled kernal and attendant files, not to mention a non-recursive /boot directory. I had problems with the images: first, as a first time gentoo participant, I attempted a network connected install, but had the Universal CD instructions. Though sought, the NON-Universal CD install is ripe with opportunity for improvement. I then rm -rf /dev/hda1 and /dev/hda3 (and yes, this is coincidentally like the example...), aka rm -rf / , while: mount -t ext3 /dev/hda3 /mnt/gentoo && mkdir /mnt/gentoo/boot && mount /dev/hda1 /mnt/gentoo/boot/ And so forth...
/boot/boot is a symlink to /boot. This makes bootloader configuration a heck of a lot easier. It won't cause any problems, and it's there on purpose.
