On Donnerstag, 23. August 2007, James Ausmus wrote: > On 8/22/07, Volker Armin Hemmann <[EMAIL PROTECTED]> wrote: > > On Donnerstag, 23. August 2007, James Ausmus wrote: > > > On 8/22/07, Volker Armin Hemmann <[EMAIL PROTECTED]> > > > wrote: <snip> > > > > > > > In your case I would remove the kernel sources, reinstall them, and > > > > start with a new, clean config - I had a severe case of 'why are half > > > > of my options missing' a few weeks ago ... > > > > > > There's no need to remove the kernel *sources* - just do this to reset > > > your kernel tree to a "virgin" state: > > > > > > cd /usr/src/linux > > > mv .config .config.old > > > make mrproper > > > make distclean <optional> > > > > > > and that'll delete config files and any generated/built files - the > > > make distclean will also removed editor backup files and any leftover > > > patch files - just an extra level of sanitization... > > > > in theory. Yes. In practice I have seen that fail. > > Fair enough. :) > > If you want to be the most safe (and don't care about some potentially > unneeded hard drive thrashing), then emerge -C the kernel, then do an > rm -Rf /usr/src/linux, which will make sure all the non-portage > installed/"touched last" files get removed as well, such as .config > files and intermediate build files
no, first rm -rf /usr/src/linux and then emerge -C the sources (or just emerge them again) that is way faster than unmerging first... rm a dir is fast, unmerging thousands of files not. -- [EMAIL PROTECTED] mailing list
