From: "Vegard Nossum" <vegard.nossum@gmail.com>
To: saravanakumar <saravanakumar.s@teclever.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-mips@linux-mips.org" <linux-mips@linux-mips.org>
Subject: Re: kernel configuration_ help
Date: Thu, 3 Jul 2008 16:50:40 +0200 [thread overview]
Message-ID: <19f34abd0807030750n31a3bc3t8609f58c9c1f7c7@mail.gmail.com> (raw)
In-Reply-To: <1214997772.16081.3.camel@teclever-desktop>
On Wed, Jul 2, 2008 at 1:22 PM, saravanakumar
<saravanakumar.s@teclever.com> wrote:
> hai,
> i want my usb to access the root file system,for that what are the
> changes to be done in kernel code, and in the configuration, i think
> changes to be done in do_mount.c for root delay, if its correct where to
> give the delay.
Hi,
If I understand correctly, you have your root filesystem on a USB
device. It seems that you must pass the rootdelay= option on the
kernel command line. No changes to the code should be necessary.
From Documentation/kernel-parameters.txt:
rootdelay= [KNL] Delay (in seconds) to pause before attempting to
mount the root filesystem
Try 10 seconds first, then go lower until it stops working.
It seems that this unfortunate hack is necessary because USB devices
can take an indefinite amount of time to register themselves once
connected.
You will of course also need the relevant config options. Make sure
your filesystem is selected, Advanced partition selection, USB, and
SCSI disk support.
Good luck!
Vegard
--
"The animistic metaphor of the bug that maliciously sneaked in while
the programmer was not looking is intellectually dishonest as it
disguises that the error is the programmer's own creation."
-- E. W. Dijkstra, EWD1036
WARNING: multiple messages have this Message-ID (diff)
From: "Vegard Nossum" <vegard.nossum@gmail.com>
To: saravanakumar <saravanakumar.s@teclever.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-mips@linux-mips.org" <linux-mips@linux-mips.org>
Subject: Re: kernel configuration_ help
Date: Thu, 3 Jul 2008 16:50:40 +0200 [thread overview]
Message-ID: <19f34abd0807030750n31a3bc3t8609f58c9c1f7c7@mail.gmail.com> (raw)
Message-ID: <20080703145040.JHbLBctkOoltOpjDVU1BjE0BbEAFrEIdjkIrjIGWNKg@z> (raw)
In-Reply-To: <1214997772.16081.3.camel@teclever-desktop>
On Wed, Jul 2, 2008 at 1:22 PM, saravanakumar
<saravanakumar.s@teclever.com> wrote:
> hai,
> i want my usb to access the root file system,for that what are the
> changes to be done in kernel code, and in the configuration, i think
> changes to be done in do_mount.c for root delay, if its correct where to
> give the delay.
Hi,
If I understand correctly, you have your root filesystem on a USB
device. It seems that you must pass the rootdelay= option on the
kernel command line. No changes to the code should be necessary.
next prev parent reply other threads:[~2008-07-03 14:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-02 11:22 kernel configuration_ help saravanakumar
2008-07-03 14:50 ` Vegard Nossum [this message]
2008-07-03 14:50 ` Vegard Nossum
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=19f34abd0807030750n31a3bc3t8609f58c9c1f7c7@mail.gmail.com \
--to=vegard.nossum@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=saravanakumar.s@teclever.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox