From: Josh McKinney <forming@home.com>
To: linux-kernel@vger.kernel.org
Subject: Re: About rebuild 2.4.x kernel to support SMP.
Date: Thu, 26 Apr 2001 15:16:15 -0500 [thread overview]
Message-ID: <20010426151615.A19046@home.com> (raw)
In-Reply-To: <611C3E2A972ED41196EF0050DA92E0760265D56A@EXCHANGE2>
In-Reply-To: <611C3E2A972ED41196EF0050DA92E0760265D56A@EXCHANGE2>; from YipingChen@via.com.tw on Thu, Apr 26, 2001 at 10:59:44PM +0800
It seems to me that you never installed the new kernel. Try 'make install'
or manually cp'ing the vmlinuz and system.map yourself.
On approximately Thu, Apr 26, 2001 at 10:59:44PM +0800, Yiping Chen wrote:
>
> I know it's not proper ask such question here. But I don't know where can I
> post this question.
> I download RedHat 7.1 last week, and install it in my dual-CPU enviroment.
> I try to rebuild kernel that support SMP in kernel 2.4.2 today , but it
> failed.
> The following is what I did.
> ========================================
> 1. Install Red Hat 7.1 in my dual-CPU environment
> 2. type 'uname -a' , the following is the result:
> Linux lab5-1 2.4.2-2smp #1 SMP Sun Apr 8 20:21:34 EDT 2001 i686 unknown
> 3. cd /usr/src/linux-2.4 (becuase Red Hat link the 2.4.2 kernel source to
> linux-2.4)
> 4. make mrproper
> 5. make menuconfig (set SMP and RTC)
> 6. make dep
> 7. make clean
> 8. make bzImage
> 9. make modules
> 10. make modules_install
> 11. edit /etc/lilo.conf
> 12. run lilo
> 13. reboot, choose new kernel to boot the system, type 'uname -a'
> Linux lab5-1 2.4.2-2 #1 SMP Wed Apr 25 18:56:05 CST 2001 i686 unknown
>
> My question is why the result of 'uname -r' is not "2.4.2-2smp" , but
> "2.4.2-2"
> Whether I forgot to do something?
> It seems that when we compile the 2.4.2 kernel, it will not use -D__SMP__
> argument now.
> (because I didn't see it in /usr/src/linux-2.4/Makefile, and I didn't see it
> when I did 'make bzImage')
> If someone ever build 2.4.x kernel which support SMP, please teach me how to
> do it.
> Thanks!!
>
> --------------------------------------------------
> Yiping Chen
> VIA Technologies, Inc.
> LAN Software
> 533 Chung Cheng Road 8F
> Hsin Tien, Taipei
> Taiwan
> TEL : 886-2-22185452 EXT.7512
> FAX : 886-2-22187527
> E-mail : YipingChen@via.com.tw
>
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
--
Linux, the choice | There was a young man from Stamboul Who
of a GNU generation -o) | boasted so torrid a tool That each female
Kernel 2.4.3-ac1 /\ | crater Explored by this satyr Seemed
on a i586 _\_v | almost unpleasantly cool.
|
next prev parent reply other threads:[~2001-04-26 21:01 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-26 14:59 About rebuild 2.4.x kernel to support SMP Yiping Chen
2001-04-26 15:20 ` Vivek Dasmohapatra
2001-04-26 20:16 ` Josh McKinney [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-04-26 15:36 Yiping Chen
2001-04-26 15:48 ` Vivek Dasmohapatra
2001-04-26 16:11 ` Alan Shutko
2001-04-26 16:03 ` kernel
2001-04-27 11:27 ` Johan Kullstam
2001-04-27 6:02 ` Kevin Buhr
2001-04-26 16:24 Yiping Chen
2001-04-26 16:41 ` Vivek Dasmohapatra
2001-04-27 11:53 Yiping Chen
2001-04-27 13:01 ` Feng Xian
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=20010426151615.A19046@home.com \
--to=forming@home.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox