1 |
ny6p01@×××××.com wrote: |
2 |
> On Fri, Feb 24, 2012 at 11:02:38PM +0000, Neil Bothwick wrote: |
3 |
>> On Fri, 24 Feb 2012 14:11:24 -0800, ny6p01@×××××.com wrote: |
4 |
>> |
5 |
>>> Or just import .config into the 'New' directory, and run plain ol' make |
6 |
>>> menuconfig. Menuconfig will import what it can from the old config. From |
7 |
>>> what I've read of the docs, make oldconfig is the dangerous part that |
8 |
>>> should be avoided between substantial kernel updates. |
9 |
>> |
10 |
>> make oldconfig is not the risk, importing the old config is. oldconfig |
11 |
>> tries to convert the old config to suit the new kernel, with a success |
12 |
>> rate probably in excess of 99%, despite what has been written about it. |
13 |
>> |
14 |
>> Using the old .config without make oldconfig is a good way of getting |
15 |
>> the worst of both worlds. |
16 |
>> |
17 |
>> |
18 |
>> -- |
19 |
>> Neil Bothwick |
20 |
>> |
21 |
>> Windows Error #56: Operator fell asleep while waiting. |
22 |
> |
23 |
> |
24 |
> I don't mean to be petty, so forgive me - but I needed to check to see if |
25 |
> I'd misread the kernel upgrade guide. So I went back and checked the guide, |
26 |
> and I was confirmed in my impression. From the guide: |
27 |
> |
28 |
> #Start Quotes |
29 |
> It is sometimes possible to save time by re-using the configuration file |
30 |
> from your old kernel when configuring the new one. Note that this is |
31 |
> generally unsafe -- too many changes between every kernel release for this |
32 |
> to be a reliable upgrade path. |
33 |
> |
34 |
> The only situation where this is appropriate is when upgrading from one |
35 |
> Gentoo kernel revision to another. For example, the changes made between |
36 |
> gentoo-sources-2.6.9-r1 and gentoo-sources-2.6.9-r2 will be very small, so |
37 |
> it is usually OK to use the following method. However, it is not appropriate |
38 |
> to use it in the example used throughout this document: upgrading from 2.6.8 |
39 |
> to 2.6.9. Too many changes between the official releases, and the method |
40 |
> described below does not display enough context to the user, often resulting |
41 |
> in the user running into problems because they disabled options that they |
42 |
> really didn't want to. |
43 |
> |
44 |
> To reuse your old .config, you simply need to copy it over and then run make |
45 |
> oldconfig. In the following example, we take the configuration from |
46 |
> gentoo-sources-2.6.9-r1 and import it into gentoo-sources-2.6.9-r2. |
47 |
> |
48 |
> A much safer upgrading method is to copy your config as previously shown, |
49 |
> and then simply run make menuconfig. This avoids the problems of make |
50 |
> oldconfig mentioned previously, as make menuconfig will load up your |
51 |
> previous configuration as much as possible into the menu. Now all you have |
52 |
> to do is go through each option and look for new sections, removals, and so |
53 |
> on. By using menuconfig, you gain context for all the new changes, and can |
54 |
> easily view the new choices and review help screens much easier. You can |
55 |
> even use this for upgrades such as 2.6.8 to 2.6.9; just make sure you read |
56 |
> through the options carefully. Once you've finished, compile and install |
57 |
> your kernel as normal. |
58 |
> |
59 |
> #End Quotes |
60 |
> |
61 |
> |
62 |
> Terry |
63 |
> |
64 |
> |
65 |
|
66 |
|
67 |
That is true BUT the docs are for 100% certainty. Well, 99% at least. |
68 |
They almost always have the safest way to do anything but not |
69 |
necessarily the most used way. There are lots of things I do |
70 |
differently from the docs and my system generally works fine, except for |
71 |
the little roaches that scurry about from time to time. |
72 |
|
73 |
If you want a drop dead, almost as sure as the Sun comes up in the East |
74 |
approach, go by the docs. If you want to save some time for most |
75 |
general usage, do it the way us goofy geeks do it. Some of us know some |
76 |
neat shortcuts. |
77 |
|
78 |
Dale |
79 |
|
80 |
:-) :-) |
81 |
|
82 |
-- |
83 |
I am only responsible for what I said ... Not for what you understood or |
84 |
how you interpreted my words! |
85 |
|
86 |
Miss the compile output? Hint: |
87 |
EMERGE_DEFAULT_OPTS="--quiet-build=n" |