David Haller <gen...@dhaller.de> writes: [...]
>>I've never used genkernel, but from what I understand it builds >>everything + the kitchen sink.. so should get the right drivers >>hopefully. > > Actually no, you can quite easily configure it to just the tedious > work. First, thanks for the cogent and helpful post. Now about the statements above. Its hard to tell what you mean there. I said I figured since genkernel builds so much stuff, its a good chance I will have the stuff I need to get booted. You start by saying `Actually no,' so do you mean there is a pretty good chance I will NOT get the drivers I need? If so, then I may be wasting my time with genkernel. Or were you just saying that if you configure genkernel correctly you can keep it from creating so much unneded junk? > Currently I use this: > > 1. install new kernel sources (in my case vanilla-sources) > 2. copy over old config from last source tree, /boot/, /proc/config.gz > whatever > 3. run 'make oldconfig' > 4. optionally note down some new options and then checkup on them using > 'make menuconfig' and searching for the noted options > it's this step I want to be able to do why I configured genkernel as > I did (see below) > 5. run 'genkernel --kerneldir=. all', but note config below! > 6. check /boot/ and /boot/grub*/ if all went right > 7. recompile neccessary out-of-tree drivers like e.g. > x11-drivers/nvidia > 8. done > > If I just reconfigure, I start at step 4, change the localversion too > in menuconfig. If something breaks, I run 'make clean', save config > and run 'make mrproper' restore config, etc. That is a nice walk thru... I can't say I understand all of it, and currently I have a genkernel compile running... (It seems to take a really long time to complete) So probably it'll be tomorrow. Nice to see. Lots of it is default. I think I would like to have a look at /usr/src/linux/.confg if that is not getting too snoopy. I realize it will not be the same as mine but what is > ==== delcomments /etc/genkernel.conf ====[1] > OLDCONFIG="no" > MENUCONFIG="no" [...] > Of course you must adapt the options for your needs, esp. those for > the initrd if you boot from e.g. a md-device and some such. > > I don't actually use the generated initrd, but having them in /boot > with less that 3MB in my case is ok and might come in handy when > something fails. I have'nt used an initrd for at least 15 yrs. So all pretty much like new stuff. > For me, this has worked nicely the last years. Esp. generating the > grub1 entries and handling the symlinks to the current and last > kernel, initrd and System.map works flawlessly[2]. OK, that sounds comforting, and promising [...] > [2] ok, if you manually prune versions from the middle, you'll need to > set the .old symlinks back to an older version (or the current?), > haven't checked that yet, but setting it to the previous remaining > version works nicely. > > I still haven't checked too, if you could have this setup: No, not like that... In this case there has been no OS before. This a fresh install after a hiatus from gentoo of about a year. I did run gentoo for 4-5 yrs awhile back.. I've been running primarily openindiana (x86 solaris-11* ish, powered by illumos) I like that zfs file system. But also have kept my home mail setup on Debian. I've tinkered fairly extensively with `lubuntu' (Notice the `el'(l) in front... supposed to indicate a lightish version of ububtu) It defaults to the lxde desktop which I like a lot too. > > title=Gentoo current kernel > root (hd0,1) > kernel /boot/kernel OPTIONS... > [initrd /boot/initramfs] I also see you are using legacy grub. I moved to grub2 some 5-6 mnths ago. But not on Openindiana > and that new versioned entries would be put at the "HERE" or at the top. > > I marked the 'initrd' stuff as optional with the [], as I don't use > an initrd. I'm not really sure how blend your approach into grub2 but I could drop back to legacy grub > And maybe some other boot options (e.g. for another distro or Winders) > sprinkled in at some location. > > Anyway, generally genkernel is a great help and occasionally > pruning/reordering entries in the grub1 /boot/grub/menu.lst is easy, > just delete/move stuff around with $EDITOR :) > > I never understood why grub2 chucked out the major advantage grub1 had > over lilo: not needing to re-install the boot-sector / stage1 of the > bootloader after every change to the config... Beats me still today. > Which is why I continue to use grub1, which can do all I need (and > more) just nicely. Thank you very much. Some of the debian based OSs' out there do not make that too easy... (staying with grub1) But it seems easily done in gentoo. Thanks again for the helpful post.
