[uClinux-dev] Rootfs mount order
mike at steroidmicros.com
Thu Aug 11 17:57:24 EDT 2005
Thanks for the answer. I am not using a standard Linux boot loader
(dBUG), so I can't pass boot parameters, but I was able to track down the
CONFIG option for "compiled in" boot parameters and it works!
>>From: uclinux-dev-bounces at uclinux.org [mailto:uclinux-dev-
>>bounces at uclinux.org] On Behalf Of Phil Wilshire
>>Sent: August 11, 2005 2:21 PM
>>To: uClinux development list
>>Subject: Re: [uClinux-dev] Rootfs mount order
>>I have one answer for you
>> rootfstype=romfs should do the trick for you.
>> Phil Wilshire
>>Mike Lavender wrote:
>>> I have a system with a small amount of flash and a ton of RAM. I am
>>>using some of the flash for a user filesystem with mtd and JFFS2 and I am
>>>using a romfs in ram which is also mounted on mtd. I have run into a
>>>problem when the kernel attempts to mount the root filesystem on the mtd
>>>device. The kernel attempts to mount each of the enabled filesystems in
>>>"order" (i.e. ext2 first, then jffs2, then romfs). The problem is that
>>>first attempts to mount jffs2 and it does not fail gracefully (i.e. spits
>>>out a ton of "jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found
>>>errors). I have set the debugging verbosity to 0 (as per 0 = quiet,
>>>2=noisy) in the JFFS2 configuration option.
>>>Is there a way to control the order that the kernel attempts to mount the
>>>rootfs? from a configuration option?
>>>Is there a way to get JFFS2 to fail without printing a million messages?
>>>uClinux-dev mailing list
>>>uClinux-dev at uclinux.org
>>>This message was resent by uclinux-dev at uclinux.org
>>uClinux-dev mailing list
>>uClinux-dev at uclinux.org
>>This message was resent by uclinux-dev at uclinux.org
More information about the uClinux-dev