New Linux Configuration Tool

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."

Comments

Whats good for linux is good for open source

[jormurgandr]

It's nice to see productive discussion (rather than the oh-so-common flame wars) taking place to the benefit of linux/open-source. Hopefully this will provide a much-needed improved configuration tool for linux, and will also demonstrate to the "closed-source" community just how beneficial open-source really is.

Re:Whats good for linux is good for open source

[GigsVT]

I think a lot of what may seem a flame war is actually productive discussion. The LKML has a really pretty nice way of having productive conversations that sometimes border on flame wars. Between Linus and Alan Cox, things usually seem to head in reasonable directions, even if they start out badly. Of course, any one message taken out of a thread may seem pretty bad, but it's important to follow the threads through to the end to get the whole picture.

Re:just a kernel tool

[Unknown Lamer]

The title of the article is correct; remember that the kernel is Linux, and the OS is GNU/Linux. So this is a Linux configuration tool. So what you want is a universal GNU/Linux configuration tool (I know, I know, now you all hate me and want me to die). The problem with writing this universal tool is that every program uses a different configuration syntax, so you would have to write each sub-tool separately. Alternatively, all configuration done with the tool could be stored in a special format and translated to the real config format by a conversion program.

Re:just a kernel tool

[LinuxGeek8]

what linux needs is a universal way of configuring a linux system so that you can pick any disto you want without worrying about how hard will it be to configure.

If you don't mind, I'd like to say "NO".
I prefer it the way the Linux distro's do it now. Like Mandrake, which even recognises printers, and sets up xawtv for your tvcard during install. These are not kernel issues, but userspace issues. Most distro's ship nowadays with every driver as a module. If the installer detects everything, you should be fine.
There are just a few issues, where it would make sense. I really like the way FreeBSD handles network card drivers. It seems to detect them fine, and load the right driver. I'm not sure how it can be done, but it happens. That's something in kernel-space, and I hope it will get included in Linux too.

Re:Who cares?

[tubabeat]

Hmmm, but isn't this new tool a backend which permits new interfaces to kernel configuration to be built which interact with it?

Surely then, it is a logical step for someone (with __lots__ of time) to build a frontend which scans the machine's hardware and automatically makes the right choices? Perhaps even preventing configurations which would prevent the kernel from booting?