linux-kernel - Re: Driver-Core: devtmpfs - remove EXPERIMENTAL and enable it by default

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 for Android: free password hash cracker in your pocket

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

Date:	Fri, 15 Jan 2010 10:03:41 -0800
From:	Greg KH <greg@...ah.com>
To:	Arjan van de Ven <arjan@...radead.org>
Cc:	Kay Sievers <kay.sievers@...y.org>,
	linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: Driver-Core: devtmpfs - remove EXPERIMENTAL and enable it by
 default

On Fri, Jan 15, 2010 at 06:56:38AM -0800, Arjan van de Ven wrote:
> On Thu, 14 Jan 2010 22:47:57 +0100
> Kay Sievers <kay.sievers@...y.org> wrote:
> 
> > From: Kay Sievers <kay.sievers@...y.org>
> > Subject: Driver-Core: devtmpfs - remove EXPERIMENTAL and enable it by
> > default
> > 
> > All major distros enable devtmpfs on recent systems, so remove
> > the EXPERIMENTAL flag, and enable it by default to reflect how it
> > is used today.
> 
> removing experimental is fine... but setting it by default is a bit
> over the top and very inconsistent with how the 'default' option is
> used.

Why?  All major distros need this at boot time, and as we have been
through a release cycle with the config option, anyone who is
incrementally updating will continue with their existing value.  But new
people coming in, will get the option as it is most likely required to
boot properly.

Makes sense to me.

thanks,

greg k-h
--
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/