> You should
> - make bzImage the default for 2.2.x and later, since it does
> run most of the time and zImage shuold be considered the
> unusual case.
NO !!!
As far as my Toshiba T2110 is concerned, kernels made with your
favoured "make bzImage" will NOT boot! Period!
When somebody manages to fix bzImage so it ALWAYS works, then one can
consider making it the default, but not otherwise...
> - leave out 'make clean' for later 2.2.x and 2.3.x kernels,
> since I think that has been made obsolete (my kernel compiles
> just fine w/o it and make xconfig does not say anything about
> it any more)-
I would tend to be cautious about "I think" on something like that, as
some configuration changes WILL result in faulty compiles if that
"make clean" is omitted.
> - prompt for dev kernels, e.g. like this:
> CAUTION: You are trying to build a DEVELOPMENT kernel. This means that
> there is no guanrantee that it will even compile correctly.
> Do you know exactly, what you are doing?
> Have you checked www.kernelnotes.org for any known broken
> feature that can chew your system up and laugh at you?
> anwer 'yes' or 'NO':
No comment...
> Maybe this prevents some people from thinking 'Well, three's
> more'n two, so let's check out...'
I've always thought that the stable series should have a LATER number
than the development one for precicely this reason...
Best wishes from Riley.
+----------------------------------------------------------------------+
| There is something frustrating about the quality and speed of Linux |
| development, ie., the quality is too high and the speed is too high, |
| in other words, I can implement this XXXX feature, but I bet someone |
| else has already done so and is just about to release their patch. |
+----------------------------------------------------------------------+
* ftp://ftp.MemAlpha.cx/pub/rhw/Linux
* http://www.MemAlpha.cx/kernel.versions.html
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/