From: Samuel Flory <sflory@rackable.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Wesley Wright <wewright@verizonmail.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] USB HardDisk Booting 2.4.20
Date: Thu, 30 Jan 2003 14:35:01 -0800 [thread overview]
Message-ID: <3E39A895.9000602@rackable.com> (raw)
In-Reply-To: <1043952432.31674.22.camel@irongate.swansea.linux.org.uk>
Alan Cox wrote:
>On Thu, 2003-01-30 at 17:27, Wesley Wright wrote:
>
>
>>My tests show that it seems to work, and I haven't noticed any odd side
>>affects by initcall-ing the usb devices (concern over this topic is why
>>I enabled it for static USB MSD only).
>>
>>Does this seem a reasonable solution, or does anyone have something more
>>elegant?
>>
>>
>
>Is there a reason for not using initrd for this. That should let you
>use any kind of root device even ones requiring user space work before
>the real root is mounted.
>
>
The problem I've seen is there is a several second delay before the
usb device is availble. My solution was to stick a sleep in my initrd
before attempting to mount /. A more rational patch might be to retry
mounting / after a few seconds delay before giving up. I think I saw
patch doing this on the usb list.
--
There is no such thing as obsolete hardware.
Merely hardware that other people don't want.
(The Second Rule of Hardware Acquisition)
Sam Flory <sflory@rackable.com>
next prev parent reply other threads:[~2003-01-30 22:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-30 17:27 Wesley Wright
2003-01-30 18:47 ` Alan Cox
2003-01-30 22:35 ` Samuel Flory [this message]
2003-01-31 2:21 ` Willy Tarreau
2003-02-01 15:00 ` Wesley Wright
2003-01-30 22:51 ` Wakko Warner
[not found] ` <mailman.1043967125.21672.linux-kernel2news@redhat.com>
2003-01-31 1:28 ` Pete Zaitcev
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=3E39A895.9000602@rackable.com \
--to=sflory@rackable.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=wewright@verizonmail.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
Powered by JetHome