Linux Configuration Tool

[TheQuirk]

http://developers.slashdot.org/developers/02/10/12/1926242.shtml?tid=106

[Calum]

quote:New Linux Configuration Tool
Posted by timothy on Saturday October 12, @03:39PM
from the usable dept.
paul.dunne writes "Looks like we are finally well on the way to getting a replacement for the old Linux configuration tools. Details in a thread on the linux-kernel mailing list. Basically, Linus likes it; it's written in C, so there are no "language issues"; and feedback on the mailing list so far seems positive and constructive."

 

quote:Subject: linux kernel conf 0.8
From: Roman Zippel ([email protected])
Date: Tue Oct 08 2002 - 16:40:43 AKDT


Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Next message: Brendan J Simon: "Re: [kbuild-devel] Re: RfC: Don't cd into subdirs during kbuild"
Previous message: Brian F. G. Bidulock: "Re: [PATCH] Re: export of sys_call_table"
Next in thread: Roman Zippel: "Re: linux kernel conf 0.8"

--------------------------------------------------------------------------------


Hi,


At http://www.xs4all.nl/~zippel/lc/ you can find the latest version of
the new config system.


As already mentioned before lkc is pretty much ready (except for kbuild
integration).
Linus, do you have any interest in merging it in the near future? If
not, what's missing?
The 2.5.40 release showed again, how bad three different parsers are, so
I think it's important to fix this finally for 2.6.


Changes this time:
- update to 2.5.41
- better error handling
- I introduced a few automaticly defined symbols (currently ARCH,
KERNELRELEASE, UNAME_RELEASE), which are currently only used for the
default location of the default config (e.g.
"/boot/config-$UNAME_RELEASE" or "arch/$ARCH/defconfig"), which are
currently still hardcoded, but could later be moved into Build.conf.
- more fine tuning
- I had to use my own Makefile again (Rules.make is slowly driving me
insane).


bye, Roman

just to whet people's appetites...

[DC]

Don't link to slashdot - link to the article. Or both.

Anyway, I fail to see the big deal. It's moderatly useful for kernel developers, I guess, and maybe a little better for the end user (those who compile kernels), but not much. AFAIK, it doesn't really bring anything new.

Please feel free to correct me if I'm wrong - if it IS a big deal I'd be happy to know why.