From: Hua Wen <wenh@taec.com>
To: Jun Sun <jsun@mvista.com>
Cc: linux-mips@oss.sgi.com
Subject: Re: Upgrade kernel from release 2.2 to 2.4.?
Date: Fri, 17 Aug 2001 12:20:27 -0700 [thread overview]
Message-ID: <3B7D6E7B.9994255@taec.com> (raw)
In-Reply-To: 3B7D57E4.D7B14D63@mvista.com
Thank you very much, Jun.
One more thing -- we've made quite some changes in
2.2.1 so I wonder what would be the best way to
upgrade. I'm thinking:
1> check out new kernel, use "merge directories"
function from emacs, or
2> use "cvs import" to import the new kernel to
our local cvs repository, then merge with our
local changes by "cvs update/co -j"..
Any comments/suggestions?
Thanks!
-Hua
> >
> > We made changes to linux/MIPS kernel 2.2.1 for our
> > system and it's been running well so far. We now
> > plan to upgrade the kernel to 2.4.X. The question
> > is:
> >
> > Which sub release of 2.4 is more stable and is
> > recommended to use?
> >
>
> I suggest you use the latest CVS head. So far it is usually the head that has
> the most bug fixes, and really not much dramatic stuff introduced.
>
> Jun
next prev parent reply other threads:[~2001-08-17 19:20 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-06 16:25 2.4.3 kernel George Gensure
2001-05-06 16:25 ` George Gensure
2001-05-06 19:47 ` DELETE CPMSA
2001-05-06 19:47 ` DELETE CPMSA
2001-05-06 23:26 ` install in the first hard disk Yoshi.-K
2001-05-06 23:26 ` Yoshi.-K
2001-05-06 23:36 ` Keith M Wesolowski
2001-05-08 15:19 ` 2.4.3 kernel Florian Lohoff
2001-08-17 2:17 ` Upgrade kernel from release 2.2.1 to 2.4.? Hua Wen
2001-08-17 2:17 ` Hua Wen
2001-08-17 17:32 ` Upgrade kernel from release 2.2 " Hua Wen
2001-08-17 17:32 ` Hua Wen
2001-08-17 17:44 ` Jun Sun
2001-08-17 19:20 ` Hua Wen [this message]
2001-08-17 21:26 ` Jun Sun
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=3B7D6E7B.9994255@taec.com \
--to=wenh@taec.com \
--cc=jsun@mvista.com \
--cc=linux-mips@oss.sgi.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 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.