| 1 |
On Fri, 07 Aug 2015 04:40:12 -0400, Felix Miata wrote: |
| 2 |
|
| 3 |
> > Didn't we cover this already? You have GRUB installed to boot your |
| 4 |
> > other distros, all you need to do is add a stanza for Gentoo to your |
| 5 |
> > existing menu.lst. |
| 6 |
> |
| 7 |
> Subject only got touched. That's all I *need* to do. :-) |
| 8 |
|
| 9 |
Yes :) |
| 10 |
|
| 11 |
> My machines have lots of installations[1], so my master bootloaders |
| 12 |
> only load default kernels (via symlink vmlinuz-cur), installation |
| 13 |
> kernel(s), memtest(s), or chainload. I maintain these manually. |
| 14 |
> |
| 15 |
> Bootloaders on my / partitions are chainloaded to for choosing among |
| 16 |
> multiple installed kernels per distro. Their menus are typically |
| 17 |
> maintained automatically by them rather than me. |
| 18 |
|
| 19 |
With GRUB2 you can simply source the other menu files from the main |
| 20 |
menu, I don't know if dinoGRUB had this feature. |
| 21 |
|
| 22 |
> >> Why is root=/dev/ram0 real_root= in the sample/prototype? |
| 23 |
> |
| 24 |
> > That's for using an initrd, specifically the one produced by |
| 25 |
> > genkernel. With no initrd you simply give the actual root device. |
| 26 |
> |
| 27 |
> I can't remember ever using a distro without an initrd before Gentoo, or |
| 28 |
> needing /dev/ram* to boot except for an installation kernel. |
| 29 |
|
| 30 |
Like I said, it's the genkernel way of doing things. I never liked |
| 31 |
genkernel so never had to deal with that. I used to create my own |
| 32 |
initramfs's, but dracut made it too easy so I let that do all the work |
| 33 |
now. |
| 34 |
|
| 35 |
|
| 36 |
-- |
| 37 |
Neil Bothwick |
| 38 |
|
| 39 |
Of all the people I've met you're certainly one of them |
Archives