From: Samuel Flory <sflory@rackable.com>
To: Daniel.A.Christian@NASA.gov
Cc: John Appleby <john@dnsworld.co.uk>, linux-kernel@vger.kernel.org
Subject: Re: 2.4.21-rc7 SMP module unresolved symbols
Date: Wed, 04 Jun 2003 12:36:24 -0700 [thread overview]
Message-ID: <3EDE4A38.3050405@rackable.com> (raw)
In-Reply-To: <200306041106.01316.Daniel.A.Christian@NASA.gov>
Dan Christian wrote:
>
>"make mrproper" fixes it.
>
>For the record, I think this stinks!
>
>"make mrproper" should be an expert only utility because it does blow
>away valuable configuration information (a painfull lesson that can
>only be learned "the hard way", since the README neglicts to mention
>this). For that matter, the README makes it look like creating a
>config from scratch (all 1500+ options) is no big deal!
>
>
Most developers have a std config file that they simply copy over, and
run "make oldconfig". This is why menuconfig, and xconfig get broken
every few patches.
--
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-06-04 19:27 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <434747C01D5AC443809D5FC5405011314BEC@bobcat.unickz.com>
2003-06-04 18:06 ` 2.4.21-rc7 SMP module unresolved symbols Dan Christian
2003-06-04 19:36 ` Samuel Flory [this message]
2003-06-04 20:00 ` Richard B. Johnson
2003-06-04 21:33 ` Alan Cox
2003-06-04 0:28 Dan Christian
2003-06-04 0:32 ` Marc-Christian Petersen
2003-06-04 16:00 ` Dan Christian
2003-06-04 5:30 ` Keith Owens
2003-06-04 8:31 ` J.A. Magallon
2003-06-04 9:34 ` Clemens Schwaighofer
2003-06-04 15:57 ` Dan Christian
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=3EDE4A38.3050405@rackable.com \
--to=sflory@rackable.com \
--cc=Daniel.A.Christian@NASA.gov \
--cc=john@dnsworld.co.uk \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox