public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Willy TARREAU <willy@w.ods.org>
To: Bill Catlan <wcatlan@yahoo.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Possible to delay boot process to boot from USB subsystem?
Date: Mon, 3 May 2004 23:05:31 +0200	[thread overview]
Message-ID: <20040503210531.GA206@pcw.home.local> (raw)
In-Reply-To: <004001c4314f$6f455a50$0202a8c0@boxa>

On Mon, May 03, 2004 at 04:44:30PM -0400, Bill Catlan wrote:
> Thanks Willy.  I like to automatic looping of Randy's patch (I had it working
> nicely on a 2.4.18 kernel) because I don't have to set a time in case one
> machine takes longer than another.

I certainly can understand this, although I've never tried it yet.

> So far, however, I haven't got Randy's patch working for a newer kernel, so I
> may try yours.
> 
> Would I only have to run make in the directory where I'm patching the file, then
> make bzImage, make modules_install, and make install from the top level to apply
> your patch?  Compiling all of my modules takes a long time, with random lock-ups
> during compile gumming up the works as well. :-/  Any tips appreciated.

No exactly, you should not run 'make' from the 'init' directory, but rather
tell 'make' where you want it to check for changes :

# make bzImage SUBDIRS=init

It will skip over other directories (such as drivers, fs, net, ...) and
only recompile below 'init'. I do this very often and it's very convenient.
However, you should not do this if you have changed certain compile options
or things that might imply different dependencies.

A hint to check if it has been correctly configured :

# nm vmlinux | grep setuptime
c01b2b80 d __setup_setuptime_setup
c01ab039 d __setup_str_setuptime_setup
c015700c b setuptime
c01b31b0 t setuptime_setup

Regards,
Willy


  reply	other threads:[~2004-05-03 21:06 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-02 23:27 Possible to delay boot process to boot from USB subsystem? Bill Catlan
2004-05-03  1:27 ` Randy.Dunlap
2004-05-03  5:17   ` Bill Catlan
2004-05-03 20:31   ` Bill Catlan
2004-05-04 18:53     ` Paulo Marques
2004-05-05 14:18       ` Bill Catlan
2004-05-03  5:34 ` Willy Tarreau
2004-05-03 20:44   ` Bill Catlan
2004-05-03 21:05     ` Willy TARREAU [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-05-04  2:32 Randy.Dunlap
2004-05-04  4:51 ` Willy Tarreau

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=20040503210531.GA206@pcw.home.local \
    --to=willy@w.ods.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=wcatlan@yahoo.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