| 1 |
On Friday 22 May 2015 00:49:54 Dale wrote: |
| 2 |
> Mike Gilbert wrote: |
| 3 |
> > On Thu, May 21, 2015 at 3:44 PM, <wabenbau@×××××.com> wrote: |
| 4 |
> >> walt <w41ter@×××××.com> wrote: |
| 5 |
> >> |
| 6 |
> >> [...] |
| 7 |
> >> |
| 8 |
> >>> Then, after I figured out that CONFIG_USER_NS is a kernel config item, |
| 9 |
> >>> requiring reinstallation of my kernel, I wasted more time figuring out |
| 10 |
> >>> (for the n'th time) that you shouldn't just change a single kernel |
| 11 |
> >>> config item and do "make" because that shortcut can break important |
| 12 |
> >>> things. |
| 13 |
> >>> |
| 14 |
> >>> No, you should do "make clean" first, and then do "make" etc. |
| 15 |
> >> |
| 16 |
> >> [...] |
| 17 |
> >> |
| 18 |
> >> I haven't done a "make clean" for years when I compiled a kernel and I |
| 19 |
> >> never had any problems. |
| 20 |
> > |
| 21 |
> > Then you have not made any critical config changes, or you have been very |
| 22 |
> > lucky. |
| 23 |
> |
| 24 |
> Then so have I. I have changed one thing a lot of times over the years, |
| 25 |
> run make and it work fine. Most of the time, it is when emerge spits |
| 26 |
> out that a option is needed for a package to work. Honestly, this is |
| 27 |
> the first time I recall hearing this should even be done. |
| 28 |
> |
| 29 |
> Dale |
| 30 |
> |
| 31 |
> :-) :-) |
| 32 |
|
| 33 |
I knew it should be done, but thought it ought to be done when you want to |
| 34 |
start with a clean slate and I didn't know if I needed to do this, or what a |
| 35 |
clean slate involved exactly. |
| 36 |
|
| 37 |
Since I run 'make oldconfig' I always assumed that I don't need a clean slate, |
| 38 |
plus updating minor versions takes seconds. |
| 39 |
|
| 40 |
So I'm the 3rd one in row to state that I haven't had any deleterious effects |
| 41 |
that I noticed. |
| 42 |
|
| 43 |
-- |
| 44 |
Regards, |
| 45 |
Mick |
Archives