From: Paulo Marques <pmarques@grupopie.com>
To: "David N. Welton" <davidw@dedasys.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] speedy boot from usb devices
Date: Mon, 02 Aug 2004 12:39:08 +0100 [thread overview]
Message-ID: <410E27DC.4090009@grupopie.com> (raw)
In-Reply-To: <87fz79xk5q.fsf@dedasys.com>
David N. Welton wrote:
> [ Please CC replies to me - thanks! ]
>
> Hi,
>
> I gather that there isn't much interest in this idea on behalf of the
> 'mainstream', because initrd is a far more flexible solution, but I
> happen to like the idea of booting quickly from a USB device, without
> wasting a bunch of time and space for an initrd, and we're using this
> in a product as well, so without further ado, I'll point you at
>
> http://dedasys.com/freesoftware/patches/
>
> where you can get blkdev_wakeup.patch
>
> Works like so: whenever a block device comes on line, it
> signals this fact to a wait queue, so that the init process
> can stop and wait for slow devices, in particular things such
> as USB storage devices, which are much slower than IDE
> devices. The init process checks the list of available
> devices and compares it with the desired root device, and if
> there is a match, proceeds with the initialization process,
> secure in the knowledge that the device in question has been
> brought up. This is useful if one wants to boot quickly from
> a USB storage device without a trimmed-down kernel, and
> without going through the whole initrd slog.
>
> Comments, critiques, suggestions and ideas are all welcome.
I find this to be very useful. I always found the "sleep for a while
until the device we want appears" approach very cumbersome.
However, after looking at your patch, it seems that having a
get_blkdevs() function that alloc's an array of strings, and return it
to a function that only compares the strings against the name it is
looking for and drops the array altogether, is a little overkill.
Why not have a simple blkdev_exists(char *name) function in genhd.c,
call it directly, and drop the match_root_name() function completely?
Maybe I'm missing something, but it seems much simpler...
--
Paulo Marques - www.grupopie.com
"In a world without walls and fences who needs windows and gates?"
next prev parent reply other threads:[~2004-08-02 11:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-30 21:25 [PATCH] speedy boot from usb devices David N. Welton
2004-08-02 11:39 ` Paulo Marques [this message]
2004-08-02 21:17 ` David N. Welton
2004-08-03 15:39 ` Kalin KOZHUHAROV
-- strict thread matches above, loose matches on Subject: below --
2004-08-04 22:09 Heikki Linnakangas
2004-08-04 22:32 ` David N. Welton
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=410E27DC.4090009@grupopie.com \
--to=pmarques@grupopie.com \
--cc=davidw@dedasys.com \
--cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.