On Friday 22 May 2015 00:49:54 Dale wrote: > Mike Gilbert wrote: > > On Thu, May 21, 2015 at 3:44 PM, <waben...@gmail.com> wrote: > >> walt <w41...@gmail.com> wrote: > >> > >> [...] > >> > >>> Then, after I figured out that CONFIG_USER_NS is a kernel config item, > >>> requiring reinstallation of my kernel, I wasted more time figuring out > >>> (for the n'th time) that you shouldn't just change a single kernel > >>> config item and do "make" because that shortcut can break important > >>> things. > >>> > >>> No, you should do "make clean" first, and then do "make" etc. > >> > >> [...] > >> > >> I haven't done a "make clean" for years when I compiled a kernel and I > >> never had any problems. > > > > Then you have not made any critical config changes, or you have been very > > lucky. > > Then so have I. I have changed one thing a lot of times over the years, > run make and it work fine. Most of the time, it is when emerge spits > out that a option is needed for a package to work. Honestly, this is > the first time I recall hearing this should even be done. > > Dale > > :-) :-)
I knew it should be done, but thought it ought to be done when you want to start with a clean slate and I didn't know if I needed to do this, or what a clean slate involved exactly. Since I run 'make oldconfig' I always assumed that I don't need a clean slate, plus updating minor versions takes seconds. So I'm the 3rd one in row to state that I haven't had any deleterious effects that I noticed. -- Regards, Mick
signature.asc
Description: This is a digitally signed message part.
