Re: [gentoo-user] kernel building tools

2005-05-26 Thread Holly Bostick
Mike Owen schreef:
 On 5/25/05, James [EMAIL PROTECTED] wrote:
 
Hello,

Is it OK to use 'make oldmenuconfig' to ensure that the options I had
selected in a 2.6.x kernel also are selected for the newer 2.6. kernel?
Isn't  'make oldmenuconfig' deprecated for 2.6 or does it still work?

Also I perviously used xconfig  (make xconfig) in lieu of make menuconfig,
but I cannot seem to find anything other than menuconfig. Surely
there is a nicer gui to use to build kernels and track options selected
in various kernel builds than the ole standby 'make menuconfig'.


ideas?


James

 
 
 I typically just use make oldconfig, as the number of changes from
 one version to the next aren't that great normally. Doing a make
 oldconfig will prompt you for each new feature, so once you have your
 baseline kernel set, make oldconfig is real quick. When moving between
 different -rX versions, it often won't prompt at all.
 
 Mike
 
I've actually been upgrading within a series (gentoo-sources, -r6 to
-r8), and across series (to ck-sources and mm-sources)... and been
paying attention closely to this exact issue when I did so.

And what I noticed is that when I switched the symlink and ran make
menuconfig, this was the message:

mutable linux # make menuconfig (first time config of newly installed
mm-sources, booted into gentoo-2.6.11-r8)

  HOSTCC  scripts/basic/fixdep
  HOSTCC  scripts/basic/split-include
  HOSTCC  scripts/basic/docproc
  SHIPPED scripts/kconfig/zconf.tab.h
  HOSTCC  scripts/kconfig/conf.o
  HOSTCC  scripts/kconfig/kxgettext.o
  HOSTCC  scripts/kconfig/mconf.o
  SHIPPED scripts/kconfig/zconf.tab.c
  SHIPPED scripts/kconfig/lex.zconf.c
  HOSTCC  scripts/kconfig/zconf.tab.o
  HOSTLD  scripts/kconfig/mconf
  HOSTCC  scripts/lxdialog/checklist.o
  HOSTCC  scripts/lxdialog/inputbox.o
  HOSTCC  scripts/lxdialog/lxdialog.o
  HOSTCC  scripts/lxdialog/menubox.o
  HOSTCC  scripts/lxdialog/msgbox.o
  HOSTCC  scripts/lxdialog/textbox.o
  HOSTCC  scripts/lxdialog/util.o
  HOSTCC  scripts/lxdialog/yesno.o
  HOSTLD  scripts/lxdialog/lxdialog
scripts/kconfig/mconf arch/i386/Kconfig
#
*# using defaults found in /boot/config-2.6.11-gentoo-r8*

So in fact, makeoldconfig appears to be a bit obsolete, as the new
kernel used my old kernel settings as the default. This may be because I
had installed my kernel with make install, so there *was* a config to be
found in /boot, but it did save a lot of work.

For changing series, I definitely prefer to look at the kernel config
anyway, to see what options the series' patches have added, but for
upgrading within the same series, if nothing has really changed, it's
nice to know you can just make menuconfig, save immediately (because you
don't have to do anything, but you can also confirm that the settings
really are the same if you like), and head right into make
modules_install, etc. I find that actually faster than selecting X
number of new (and usually irrelevant to me) options with make oldconfig
anyway (n, n, n, etc).

Holly
-- 
gentoo-user@gentoo.org mailing list



Re: [gentoo-user] kernel building tools

2005-05-26 Thread Neil Bothwick
On Thu, 26 May 2005 10:24:52 +0200, Holly Bostick wrote:

 For changing series, I definitely prefer to look at the kernel config
 anyway, to see what options the series' patches have added, but for
 upgrading within the same series, if nothing has really changed, it's
 nice to know you can just make menuconfig, save immediately (because you
 don't have to do anything, but you can also confirm that the settings
 really are the same if you like), and head right into make
 modules_install, etc. I find that actually faster than selecting X
 number of new (and usually irrelevant to me) options with make oldconfig
 anyway (n, n, n, etc).

The disadvantage of this approach is that you don't get to see what new
options have been added.


-- 
Neil Bothwick

I wouldn't be caught dead with a necrophiliac.


pgpPoWWWHusmF.pgp
Description: PGP signature


Re: [gentoo-user] kernel building tools

2005-05-26 Thread Holly Bostick
Neil Bothwick schreef:
 On Thu, 26 May 2005 10:24:52 +0200, Holly Bostick wrote:
 
 
For changing series, I definitely prefer to look at the kernel config
anyway, to see what options the series' patches have added, but for
upgrading within the same series, if nothing has really changed, it's
nice to know you can just make menuconfig, save immediately (because you
don't have to do anything, but you can also confirm that the settings
really are the same if you like), and head right into make
modules_install, etc. I find that actually faster than selecting X
number of new (and usually irrelevant to me) options with make oldconfig
anyway (n, n, n, etc).
 
 
 The disadvantage of this approach is that you don't get to see what new
 options have been added.
 
 
Within the series, I probably don't care (i.e., moving from
gentoo-sources -r6 to -r8, which I only even did because -r6 was removed
from Portage). For changing series (moving from gentoo-sources to
mm-sources), I do care, but that's why I manually go through the
menuconfig in that case. $DEITY knows I've compiled enough kernels to
recognize most new stuff, and if I'm not sure, I read the option's Help,
as I've always found it invaluable.

But my hardware is all pretty old-- KM266A mobo/Athlon XP 2200+ (so no
hyperthreading and no amd_64), no SATA, no PCI-e, only usb devices a
mouse and gamepad, no mp3 player/iPod, no usb keys (no usb 2.0, even),
no external hdds or devices, no bluetooth or firewire, no mobile phone,
external sound card is a C-Media 8738 (second only to my onboard VIA
8233 for bog-standardness), no TV-in or out (unless I try out the
ati-gatos drivers for TV-in, but I don't feel like being bothered yet),
no wireless, heck, no scanner or printer connected to this box (yes, I'm
a dinosaur, but I get along)-- so most new options really don't make the
first bit of difference to me, as the kernel options I need have been
stable for eons. The major ones that do change (video card, the eternal
automount-patch war between supermount, submount and hal/dbus/ivman),
are external, and for kernels like ck-sources, the new stuff
(schedulers) are generally defaulted on anyway, which is fine by me.

So I mostly just check for sightseeing purposes (to see what's
available/stablilizing for future upgrade planning), and on the off
chance I want to try something out, as well as to confirm that the
options that I must have turned off (DRM, Registers) are in fact off.

Afaics, I don't need to chase the future with the kernel; I just keep it
more-or-less up to date for increased stability and patch issues, and
looking for speed increases.

But obviously, others may have different needs.

Holly
-- 
gentoo-user@gentoo.org mailing list



Re: [gentoo-user] kernel building tools

2005-05-26 Thread Neil Bothwick
On Thu, 26 May 2005 12:18:19 +0200, Holly Bostick wrote:

  The disadvantage of this approach is that you don't get to see what
  new options have been added.
 
 Within the series, I probably don't care (i.e., moving from
 gentoo-sources -r6 to -r8, which I only even did because -r6 was removed
 from Portage). For changing series (moving from gentoo-sources to
 mm-sources), I do care, but that's why I manually go through the
 menuconfig in that case. $DEITY knows I've compiled enough kernels to
 recognize most new stuff, and if I'm not sure, I read the option's Help,
 as I've always found it invaluable.

Within a particular kernel version, there generally aren't any new
options, so it makes no difference which method you use. When the kernel
version is incremented, there may be new options added, and make
oldconfig seems a more reliable way of being notified of them than
trawling through menuconfig hoping to see them. I rarely run make
menuconfig when upgrading a kernel.


-- 
Neil Bothwick

Q. How many mathematicians does it take to change a light bulb?
A. Only one - who gives it to six Californians, thereby reducing the
problem to an earlier joke.


pgpQsRgb0qwn4.pgp
Description: PGP signature


[gentoo-user] kernel building tools

2005-05-25 Thread James
Hello,

Is it OK to use 'make oldmenuconfig' to ensure that the options I had 
selected in a 2.6.x kernel also are selected for the newer 2.6. kernel? 
Isn't  'make oldmenuconfig' deprecated for 2.6 or does it still work?

Also I perviously used xconfig  (make xconfig) in lieu of make menuconfig,
but I cannot seem to find anything other than menuconfig. Surely
there is a nicer gui to use to build kernels and track options selected
in various kernel builds than the ole standby 'make menuconfig'.


ideas?


James



-- 
gentoo-user@gentoo.org mailing list



Re: [gentoo-user] kernel building tools

2005-05-25 Thread Mike Owen
On 5/25/05, James [EMAIL PROTECTED] wrote:
 Hello,
 
 Is it OK to use 'make oldmenuconfig' to ensure that the options I had
 selected in a 2.6.x kernel also are selected for the newer 2.6. kernel?
 Isn't  'make oldmenuconfig' deprecated for 2.6 or does it still work?
 
 Also I perviously used xconfig  (make xconfig) in lieu of make menuconfig,
 but I cannot seem to find anything other than menuconfig. Surely
 there is a nicer gui to use to build kernels and track options selected
 in various kernel builds than the ole standby 'make menuconfig'.
 
 
 ideas?
 
 
 James
 

I typically just use make oldconfig, as the number of changes from
one version to the next aren't that great normally. Doing a make
oldconfig will prompt you for each new feature, so once you have your
baseline kernel set, make oldconfig is real quick. When moving between
different -rX versions, it often won't prompt at all.

Mike

-- 
gentoo-user@gentoo.org mailing list



Re: [gentoo-user] kernel building tools

2005-05-25 Thread Brett I. Holcomb
oldconfig usually works for minor version changes - just don't use it to 
go from say a 2.4 to 2.6.


xconfig needs qt installed - I get an error about qt when I try to run it.


*
* Unable to find the QT installation. Please make sure that the
* QT development package is correctly installed and the QTDIR
* environment variable is set to the correct location.
*
make[1]: *** [scripts/kconfig/.tmp_qtcheck] Error 1
make: *** [xconfig] Error 2

On Thu, 26 May 2005, James wrote:


Hello,

Is it OK to use 'make oldmenuconfig' to ensure that the options I had
selected in a 2.6.x kernel also are selected for the newer 2.6. kernel?
Isn't  'make oldmenuconfig' deprecated for 2.6 or does it still work?

Also I perviously used xconfig  (make xconfig) in lieu of make menuconfig,
but I cannot seem to find anything other than menuconfig. Surely
there is a nicer gui to use to build kernels and track options selected
in various kernel builds than the ole standby 'make menuconfig'.


ideas?


James





--
gentoo-user@gentoo.org mailing list



Re: [gentoo-user] kernel building tools

2005-05-25 Thread Nick Rout
make help

and i thinks its oldconfig, not oldmenuconfig ?


On Thu, 26 May 2005 01:16:20 + (UTC)
James wrote:

 Hello,
 
 Is it OK to use 'make oldmenuconfig' to ensure that the options I had 
 selected in a 2.6.x kernel also are selected for the newer 2.6. kernel? 
 Isn't  'make oldmenuconfig' deprecated for 2.6 or does it still work?
 
 Also I perviously used xconfig  (make xconfig) in lieu of make menuconfig,
 but I cannot seem to find anything other than menuconfig. Surely
 there is a nicer gui to use to build kernels and track options selected
 in various kernel builds than the ole standby 'make menuconfig'.
 
 
 ideas?
 
 
 James
 
 
 
 -- 
 gentoo-user@gentoo.org mailing list

-- 
Nick Rout

-- 
gentoo-user@gentoo.org mailing list