linux-kernel - [PATCH] Remove valueless definition of hard-selected RAMFS option.

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>] [day] [month] [year] [list]

Message-ID: <Pine.LNX.4.64.0708280025240.2587@localhost.localdomain>
Date:	Tue, 28 Aug 2007 00:38:40 -0400 (EDT)
From:	"Robert P. J. Day" <rpjday@...dspring.com>
To:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
cc:	Andrew Morton <akpm@...l.org>
Subject: [PATCH] Remove valueless definition of hard-selected RAMFS option.

Since CONFIG_RAMFS is currently hard-selected to "y", and since
Documentation/filesystems/ramfs-rootfs-initramfs.txt reads as follows:

"The amount of code required to implement ramfs is tiny, because all
the work is done by the existing Linux caching infrastructure.
Basically, you're mounting the disk cache as a filesystem.  Because of
this, ramfs is not an optional component removable via menuconfig,
since there would be negligible space savings."

it seems pointless to leave this as a Kconfig entry.

Signed-off-by: Robert P. J. Day <rpjday@...dspring.com>

---

  this also allows almost 300 "CONFIG_RAMFS=y" lines to be dropped
from various defconfig files.  and that horribly misleading Kconfig
help text disappears as well.  :-)

  compile tested under i386.

 fs/Kconfig        |   14 --------------
 fs/Makefile       |    2 +-
 fs/ramfs/Makefile |    2 +-
 3 files changed, 2 insertions(+), 16 deletions(-)

diff --git a/fs/Kconfig b/fs/Kconfig
index 58a0650..60d859b 100644
--- a/fs/Kconfig
+++ b/fs/Kconfig
@@ -1002,20 +1002,6 @@ config HUGETLBFS
 config HUGETLB_PAGE
 	def_bool HUGETLBFS

-config RAMFS
-	bool
-	default y
-	---help---
-	  Ramfs is a file system which keeps all files in RAM. It allows
-	  read and write access.
-
-	  It is more of an programming example than a useable file system.  If
-	  you need a file system which lives in RAM with limit checking use
-	  tmpfs.
-
-	  To compile this as a module, choose M here: the module will be called
-	  ramfs.
-
 config CONFIGFS_FS
 	tristate "Userspace-driven configuration filesystem (EXPERIMENTAL)"
 	depends on SYSFS && EXPERIMENTAL
diff --git a/fs/Makefile b/fs/Makefile
index 720c29d..500cf15 100644
--- a/fs/Makefile
+++ b/fs/Makefile
@@ -72,7 +72,7 @@ obj-$(CONFIG_JBD)		+= jbd/
 obj-$(CONFIG_JBD2)		+= jbd2/
 obj-$(CONFIG_EXT2_FS)		+= ext2/
 obj-$(CONFIG_CRAMFS)		+= cramfs/
-obj-$(CONFIG_RAMFS)		+= ramfs/
+obj-y				+= ramfs/
 obj-$(CONFIG_HUGETLBFS)		+= hugetlbfs/
 obj-$(CONFIG_CODA_FS)		+= coda/
 obj-$(CONFIG_MINIX_FS)		+= minix/
diff --git a/fs/ramfs/Makefile b/fs/ramfs/Makefile
index 5a0236e..c71e65d 100644
--- a/fs/ramfs/Makefile
+++ b/fs/ramfs/Makefile
@@ -2,7 +2,7 @@
 # Makefile for the linux ramfs routines.
 #

-obj-$(CONFIG_RAMFS) += ramfs.o
+obj-y += ramfs.o

 file-mmu-y := file-nommu.o
 file-mmu-$(CONFIG_MMU) := file-mmu.o

-- 
========================================================================
Robert P. J. Day
Linux Consulting, Training and Annoying Kernel Pedantry
Waterloo, Ontario, CANADA

http://crashcourse.ca
========================================================================
-
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/