How to discover new Linux features (was: Re: Linux 2.6.16-rc1)
In-Reply-To: <[email protected]>
Quoted 5 lines · Diego Calleja
Can I ask if it's possible to "mark" new features/important changes?
I've maintaining http://wiki.kernelnewbies.org/LinuxChanges
for three releases and the amount of changes is so big it takes hours to extract the relevant changes,
One way to find new features is to use "make oldconfig".
Say you are comparing kernels 2.6.14 and 2.6.15, trying to see what
is new. Just do this:
1. Copy a .config file into your 2.6.14 directory.
2. Run "make oldconfig" there. It doesn't really matter what answers you give so long as it runs to completion.
3. Copy that .config file to your 2.6.15 directory.
4. When you run "make oldconfig" all of the new features, drivers etc. will cause a prompt.
5. There will be some false positives if options have been renamed or moved around, but it's generally accurate.
Signature · 2 lines
Chuck Currently reading: _Noise_ by Hal Clement
Quoted 7 lines · Chuck Ebbert
Say you are comparing kernels 2.6.14 and 2.6.15, trying to see what
is new. Just do this:1. Copy a .config file into your 2.6.14 directory.
2. Run "make oldconfig" there. It doesn't really matter what answers you give so long as it runs to completion.
make it "make allconfig"
Quoted 10 lines · Alex Riesen
Quoted 7 lines · Chuck Ebbert
Say you are comparing kernels 2.6.14 and 2.6.15, trying to see what
is new. Just do this:1. Copy a .config file into your 2.6.14 directory.
2. Run "make oldconfig" there. It doesn't really matter what answers you give so long as it runs to completion.
make it "make allconfig"
Are you suggesting a new make target? 'make help' lists allyesconfig, allnoconfig, or allmodconfig (in the all* group).
Signature · 1 line
~Randy
Randy.Dunlap, Tue, Jan 24, 2006 16:13:37 +0100:
Quoted 5 lines
Quoted 5 lines
Quoted 5 lines
Say you are comparing kernels 2.6.14 and 2.6.15, trying to see what
is new. Just do this:1. Copy a .config file into your 2.6.14 directory.
Quoted 8 lines
Quoted 4 lines
Quoted 2 lines
2. Run "make oldconfig" there. It doesn't really matter what answers you give so long as it runs to completion.
make it "make allconfig"
Are you suggesting a new make target? 'make help' lists allyesconfig, allnoconfig, or allmodconfig (in the all* group).
...! allyesconfig, of course.