linux-kernel - Re: [Re: 2.6.21-rc2-mm1] #error no ROMFS backing store interface configured

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]

Message-ID: <15200.1173022514@redhat.com>
Date:	Sun, 04 Mar 2007 15:35:14 +0000
From:	David Howells <dhowells@...hat.com>
To:	Adrian Bunk <bunk@...sta.de>
Cc:	Andrew Morton <akpm@...ux-foundation.org>,
	Maciej Rutecki <maciej.rutecki@...il.com>,
	linux-kernel@...r.kernel.org
Subject: Re: [Re: 2.6.21-rc2-mm1] #error no ROMFS backing store interface configured 

Adrian Bunk <bunk@...sta.de> wrote:

> Is
> 
> CONFIG_BLOCK=y
> CONFIG_ROMFS_FS=y
> CONFIG_ROMFS_ON_BLOCK=n
> CONFIG_ROMFS_ON_MTD=y
> 
> a reasonable configuration that should be supported, or can we turn 
> CONFIG_ROMFS_ON_BLOCK always on if CONFIG_BLOCK=y?

Hmmm...  I don't really know the answer to that, apart from it depends.  On a
non-embedded device, it's entirely reasonable, I think, to turn
CONFIG_ROMFS_ON_BLOCK on if CONFIG_BLOCK is on, no questions asked.  However,
on an embedded device you might want the extra option.

David
-
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/