From: John Bradford <john@grabjohn.com>
To: sampson.fung@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 18:16:03 +0000 (GMT) [thread overview]
Message-ID: <200212211816.gBLIG3NV000880@darkstar.example.net> (raw)
In-Reply-To: <000701c2a91a$707254a0$0100a8c0@noelpc> from "Sampson Fung" at Dec 22, 2002 01:57:33 AM
> From v2.5.49 up, I can only test the compiled kernel, if it compiles at
> all, with modules disabled completely.
> Of course, I have to say that I do not try much before v2.5.49.
>
> 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.
> 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.
> Then I can try to compile my lan card as modules.
> Then try to compile my SCSI card, etc, etc.
>
> Does similar "standard templates" exist already?
No.
> Where can I search for known bugs centrally, so that I can help myself
> as much as possible?
* The mailing list archives
* Kernel Bugzilla
* (hopefully in a week or so) my new bug database which I am currently
writing.
John.
next prev parent reply other threads:[~2002-12-21 17:57 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 [this message]
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
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=200212211816.gBLIG3NV000880@darkstar.example.net \
--to=john@grabjohn.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sampson.fung@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