Sam Ravnborg wrote:
+
+config PRAMFS_NOWP
+bool Disable PRAMFS write protection
+depends on PRAMFS
+default n
+help
+ Say Y here to disable the write protect feature of PRAMFS.
n is default so default n is not needed.
If you reverse the logic (and add a default y)
Daniel Walker wrote:
On Sat, 2009-06-13 at 15:22 +0200, Marco wrote:
From: Marco Stornelli marco.storne...@gmail.com
Makefile and Kconfig.
Signed-off-by: Marco Stornelli marco.storne...@gmail.com
---
You should move this patch to 11 of 14, as I think that is the point
when the
Arnd Bergmann wrote:
On Saturday 13 June 2009, Marco wrote:
void __init mount_root(void)
{
+#ifdef CONFIG_ROOT_PRAMFS
+ if (MAJOR(ROOT_DEV) == MEM_MAJOR) {
+ if (mount_pramfs_root())
+ return;
+
+ printk(KERN_ERR VFS: Unable to
On Sun, 2009-06-14 at 10:21 +0200, Marco wrote:
Mmm...MEM_MAJOR and RAMDISK_MAJOR have the same value and pramfs works
in memory. We could simply use /dev/null (there was an error in the
submitted kconfig description, my intention was to use /dev/mem). In
that case I can use UNNAMED_MAJOR.
Marco wrote:
To enable direct
I/O at all times for all regular files requires either that
applications be modified to include the O_DIRECT flag on all file
opens, or that a new filesystem be used that always performs direct
I/O by default.
This could be done as well by just
Marco wrote:
Simply because the ramdisk was not designed to work in a persistent
environment.
One thing with persistent RAM disks is you _really_ want it to be
robust if the system crashes for any reason while it is being
modified. The last thing you want is to reboot, and find various
David Woodhouse wrote:
On Sun, 2009-06-14 at 10:21 +0200, Marco wrote:
Mmm...MEM_MAJOR and RAMDISK_MAJOR have the same value and pramfs works
in memory. We could simply use /dev/null (there was an error in the
submitted kconfig description, my intention was to use /dev/mem). In
that case I
David Woodhouse wrote:
On Sun, 2009-06-14 at 10:21 +0200, Marco wrote:
Mmm...MEM_MAJOR and RAMDISK_MAJOR have the same value and pramfs works
in memory. We could simply use /dev/null (there was an error in the
submitted kconfig description, my intention was to use /dev/mem). In
that case I
On Sat 13 Jun 2009 14:59, Wolfgang Denk pondered:
Dear Russell King,
In message 20090613102642.gb7...@flint.arm.linux.org.uk you wrote:
The other way I've seen people read out crash messages is using a
debugger to dump the kernel's log buffer directly. That seems to work
as well as
