public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Wesley Wright <wewright@verizonmail.com>
To: Willy Tarreau <willy@w.ods.org>
Cc: Samuel Flory <sflory@rackable.com>,
	Alan Cox <alan@lxorguk.ukuu.org.uk>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] USB HardDisk Booting 2.4.20
Date: 01 Feb 2003 10:00:51 -0500	[thread overview]
Message-ID: <1044111651.1965.7.camel@steven> (raw)
In-Reply-To: <20030131022151.GA25068@alpha.home.local>

> I'm personnaly using this simple patch with success with an usb disk on
> key. It adds an option "setuptime" which waits the requested amount of ms
> before booting. I use it with "setuptime=2500" and my USB works fine.
> 
> I think it could be of a more general use, and perhaps it could be
> accepted into mainstream if it doesn't break anything ?

The reason I took the other approach is that I didn't want to introduce
an arbitrary delay into my startup.  I have varying speed machines
(ranging from P90 up to Athlon 1800) and wanted a solution consistent
across all of them.  I think that you can accomplish the delay startup
through initrd without a kernel change.

Delay solutions don't directly deal with the race between mounting and
detecting the USB device though.  If I select a value to small then I
still don't get a successful mount.

Maybe this isn't a major concern for this area of the kernel though... 
at this point there really aren't any other tasks so the delay should
have very consistent results.

Thanks,
-- Wes


  reply	other threads:[~2003-02-01 14:47 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-30 17:27 [PATCH] USB HardDisk Booting 2.4.20 Wesley Wright
2003-01-30 18:47 ` Alan Cox
2003-01-30 22:35   ` Samuel Flory
2003-01-31  2:21     ` Willy Tarreau
2003-02-01 15:00       ` Wesley Wright [this message]
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=1044111651.1965.7.camel@steven \
    --to=wewright@verizonmail.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sflory@rackable.com \
    --cc=willy@w.ods.org \
    /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