On Tue, 29 May 2007 23:05:56 -0400, Denis wrote: > > I use 'gunzip -c /proc/config.gz > .config && make oldconfig' > > consistently, never had a problem. I always keep a working kernel > > in > > Oh neat-o! I didn't know there was a copy of the running config > in /proc...
It's an option you need to enable in the kernel, or you can copy .config from your current kernel source directory. > Does this basically just insert the current kernel configuration > inside the menuconfig interface of the new kernel as the starting > point? How does this play with the new kernel options that have since > appeared or those that have been eliminated? I suppose you still have > to check over every menu in the new kernel to make sure you're not > missing anything... That's what make oldconfig does, and prompts you for any new items. There's no need to run menuconfig unless you want to change something. Waiting for kernel version releases is not a good idea and the -r updates generally include security fixes. Read the Changelog and decide whether you need that particular update, some fixes only apply to certain architectures. Like many others, I have a cron task that syncs then mails the results of emerge -upvDN world to me, but I have added --changelog to that command so the mail also contains the details of each update. This runs in the early hours, so I can read it whenever it suits me during the day and apply the changes as I want. I run testing, so frequent updating is a good thing; with a stable system, weekly would be fine, but the longer you leave it the more work is involved. -- Neil Bothwick "Time is the best teacher....., unfortunately it kills all the students"
signature.asc
Description: PGP signature
