Brian Vagnoni on 6 Jul 2008 20:52:54 -0700 |
> this is why everyone needs to do at least one gentoo install. > > you do know that: > make menuconfig > > generates the .config FOR you, and is the preferred way of going about > it, don't you? it's got an ncurses interface too. it's really not that > scary. Thanks and yes I am. The problem is that the initial (generic)config created crashes when it gets to the sata drive. I'll post the exact failure point in a little bit as I'm on my way bed. That's when I got the idea of hacking the known good one. I'm lazy and don't want to have to set all those options having to guess at some of them. Opensuse is bloated I've never argued that. You don't use OpenSuse if you want a lean mean kernel. You use something like Gentoo. Yes, the make install script auto-magically adds the required and additional entries in the grub config. Yes Suse uses grub by default with lilo or whatever you want as an option. It keeps the default working kernel as your default and in the grub menu until and very smartly you know that your kernel works. -------------------------------------------------- Brian Vagnoni PGP Digital Fingerprint F076 6EEE 06E5 BEEF EBBD BD36 F29E 850D FC32 3955 -------------------------------------------------- ----- Original Message ----- From: brent timothy saner [mailto:brent.saner@gmail.com] To: Philadelphia Linux User's Group Discussion List [mailto:plug@lists.phillylinux.org] Sent: Sun, 06 Jul 2008 23:35:24 -0400 Subject: Re: [PLUG] OpenSuse 11.x Kernel Question > Brian Vagnoni wrote: > > Hi All; > > > > Having some fun here with kernel recompilation. I have the default > working 2.6.25 kernel booting up just fine. I want to add and delete > some options and then recompile. However when I go to /usr/src/linux I > find no .config file. So what I'm planning on doing is loading the > /boot/config-2.6.25.x-default and using that as my starter config. > > > > this is why everyone needs to do at least one gentoo install. > > you do know that: > make menuconfig > > generates the .config FOR you, and is the preferred way of going about > it, don't you? it's got an ncurses interface too. it's really not that > scary. > > > > Assume I have full x access. > > > > From /usr/src/linux > > > > cp /boot/config.xxxxxx .config.bak > > make mrproper > > make (bah)config ; edit said good known working config then save > > (make dep is no longer needed) > > make clean > > make all > > make modules_install install > > > > reboot > > > > i don't know if SuSE uses grub, but grub lets you use multiple > kernels. > that way if you b0rk3d something while making your new one, you at > least > have the old, unpatched/unchanged kernel to fall back on. > > > > > Or use diff to compare the 2 files, edit and recomplile? > > won't work, since the kernel is a binary file. if you had two > .configs, > it'd work, but since you don't AND since it's more recommended to > build > .configs from scratch via make menuconfig anyways... > > > > > Or just edit the good known config for the options I want to change > and recompile? > > do the above, and this. keep a copy of the good as a backup. have them > all sperate GRUB entries. > > -- > brent saner. > gpg info at http://www.notebookarmy.org/gpg.txt > (this is a shorter sig.) > > grep -i hotchicks * > > ___________________________________________________________________________ Philadelphia Linux Users Group -- http://www.phillylinux.org Announcements - http://lists.phillylinux.org/mailman/listinfo/plug-announce General Discussion -- http://lists.phillylinux.org/mailman/listinfo/plug
|
|