From: John Bradford <john@grabjohn.com>
To: sampson@attglobal.net (Sampson Fung)
Cc: linux-kernel@vger.kernel.org
Subject: Re: How to help new comers trying the v2.5x series kernels.
Date: Sat, 21 Dec 2002 19:15:36 +0000 (GMT) [thread overview]
Message-ID: <200212211915.gBLJFaZb001636@darkstar.example.net> (raw)
In-Reply-To: <000b01c2a91f$01324ff0$0100a8c0@noelpc> from "Sampson Fung" at Dec 22, 2002 02:30:13 AM
> > > I think new comers, myselft included, can make use of standard
> > > templates of kernel .config file.
> >
> > Try a minimal configuration, or the default one, (which is
> > whatever Linus uses). Avoid modular IDE for now.
> >
> Where is the default .config? I am eager to have a try.
Just do:
make distclean; make defconfig
and the default .config will be generated.
> > > First of all, "standard templates" are tested that they will be
> > > compiled without problem. They should be able to boot.
> > > They should have a working "framework" of "modules", for
> > > example, lsmod works without any problem. (And any other
> > > "required" modutils as well)
> > > They shuold supports further kernel compile. (With small incremental
> > > changes to the base "standard template").
> >
> > Sounds like an excellent job for a new kernel hacker to take on board
> > - why not make the standard templates yourself, and post them
> > to the list for each 2.5.x tree. It *would* be quite useful,
> > and save a lot of developers' time, for example, it would
> > stop a lot of people complaining about modular IDE.
>
> I can post my config as I am using common hardware config.
> But I cannot make the "framework" of "modules" working for me.
Don't worry about the hardware options - just assume that the ones in
defconfig work OK - but try to successfully build as many features
like different filesystems, etc.
John.
prev parent reply other threads:[~2002-12-21 18:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-21 17:57 How to help new comers trying the v2.5x series kernels Sampson Fung
2002-12-21 18:16 ` John Bradford
2002-12-21 18:30 ` Sampson Fung
2002-12-21 19:05 ` Sam Ravnborg
2002-12-21 20:35 ` First Bug Found : " Sampson Fung
2002-12-21 21:23 ` John Bradford
2002-12-21 21:52 ` Sam Ravnborg
2002-12-21 22:18 ` John Bradford
2002-12-24 13:33 ` Additional Bug Found--RE: " Sampson Fung
2002-12-21 19:15 ` John Bradford [this message]
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=200212211915.gBLJFaZb001636@darkstar.example.net \
--to=john@grabjohn.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sampson@attglobal.net \
/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