linux-kernel - Re: [2.6 patch] remove CONFIG

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 1 Jan 2008 13:14:13 -0500
From:	"Jon Smirl" <jonsmirl@...il.com>
To:	"Alan Cox" <alan@...rguk.ukuu.org.uk>
Cc:	"Adrian Bunk" <bunk@...nel.org>, linux-kernel@...r.kernel.org
Subject: Re: [2.6 patch] remove CONFIG_EXPERIMENTAL

On 1/1/08, Alan Cox <alan@...rguk.ukuu.org.uk> wrote:
> > I'm not claiming that all EXPERIMENTAL tags were wrong [1], but many
> > were wrong.
>
> So why not fix the wrong tags, and mark smbfs obsolete ?
>
> > Plus the fact that CONFIG_EXPERIMENTAL controlled so many different
> > things with one switch that CONFIG_EXPERIMENTAL=n .config's are really
> > rare.
>
> Agreed

CONFIG_EXPERIMENTAL is way to coarse. I always need to turn it on and
then it loses any value.

Why not encode the drivers status into the driver name so that is is
obvious when you are configuring the kernel?

Like this for a driver name:
   Compaq Smart Array 5xxx support (experimental)

Some drivers are already do this:
   Micro Memory MM5415 Battery Backed RAM support (EXPERIMENTAL)

Now the status is obvious on an item by item basis.

-- 
Jon Smirl
jonsmirl@...il.com
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/