From: "Franco \"Sensei\"" <senseiwa@tin.it>
To: David Lang <david.lang@digitalinsight.com>
Cc: Krzysztof Halasa <khc@pm.waw.pl>, Adrian Bunk <bunk@stusta.de>,
linux-kernel@vger.kernel.org
Subject: Re: [INFO] Kernel strict versioning
Date: Thu, 14 Apr 2005 14:41:44 -0500 [thread overview]
Message-ID: <425EC778.4070009@tin.it> (raw)
In-Reply-To: <Pine.LNX.4.62.0504141050460.19663@qynat.qvtvafvgr.pbz>
[-- Attachment #1: Type: text/plain, Size: 2142 bytes --]
David Lang wrote:
> there are at least a half dozen options besides SMP that have similar
> effects.
And of course if I take care of making them consistent... What I'd like
is stability. Not in the sense of having a rock-stable kernel, that of
course is already there. I'd like API stability, if API stability is
achieved, ABI is there.
> Ok, now you are talking a distro, not linux itself. different subject,
> belongs on different lists (and by the way distros already tend to do
> this type of thing)
No. I have compiled everything from scratch, every single package. Now,
every vanilla kernel brings the problem of recompiling modules for that
particular version.
> first off, if you can deploy a new kernel across 100 machines you can
> deploy new modules along with it.
>
> second, if you are applying the patch and know that it doesn't affect
> anything that the modules use you don't have to recompile the modules,
> but if you want to be safe becouse you don't know what the patch affects
> then you replace the modules as well (for all you know the patch affects
> just a module, not the base kernel.
Applying a patch to 2.6.11 making it 2.6.12 brings one thing: all
modules external to the vanilla kernel are no longer there and I have to
recompile them every time...
> again you are talking about what a distro chooses to do, go ahead and do
> this if you want, but it has no relevance to the kernel mailing list.
>
> This will be my last message on this subject, hopefully you will let
> this die or take the conversation to the mailing lists of the distros
> that you choose to use.
The global feeling about kernel is that it seems that you don't care
about the purpose of your task, which of course is not the kernel by
itself. It can't be. It's about what it does (and already does it well),
and what it provides to third-parties: the kernel and the API given to
the outside world, since the kernel is not alone... and will never be of
course! ;)
--
Sensei <mailto:senseiwa@tin.it> <pgp:8998A2DB>
<icqnum:241572242>
<yahoo!:sensei_sen>
<msn-id:sensei_sen@hotmail.com>
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 256 bytes --]
next prev parent reply other threads:[~2005-04-14 19:48 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-08 18:08 [INFO] Kernel strict versioning Franco "Sensei"
2005-04-08 19:05 ` Adrian Bunk
2005-04-12 1:02 ` Franco "Sensei"
2005-04-12 1:50 ` Adrian Bunk
2005-04-12 2:54 ` Franco "Sensei"
2005-04-12 11:28 ` Krzysztof Halasa
2005-04-12 17:22 ` Franco "Sensei"
2005-04-12 18:03 ` David Lang
2005-04-14 16:52 ` Franco "Sensei"
2005-04-14 17:57 ` David Lang
2005-04-14 19:41 ` Franco "Sensei" [this message]
2005-04-14 19:55 ` Arjan van de Ven
2005-04-14 22:33 ` Franco "Sensei"
2005-04-14 23:29 ` Al Viro
[not found] ` <425F33C2.8020301@tin.it>
2005-04-15 5:02 ` Al Viro
2005-04-14 20:01 ` Adrian Bunk
2005-04-14 22:51 ` Franco "Sensei"
2005-04-14 20:34 ` Horst von Brand
2005-04-14 22:45 ` Franco "Sensei"
2005-04-12 22:04 ` Krzysztof Halasa
2005-04-14 17:04 ` Franco "Sensei"
2005-04-12 22:43 ` Adrian Bunk
2005-04-14 17:40 ` Franco "Sensei"
2005-04-14 20:15 ` Adrian Bunk
2005-04-14 22:26 ` Franco "Sensei"
[not found] <3R6fp-7Qs-15@gated-at.bofh.it>
[not found] ` <3R71T-4S-15@gated-at.bofh.it>
[not found] ` <3Si4Q-Nh-21@gated-at.bofh.it>
[not found] ` <3SiRe-1eq-9@gated-at.bofh.it>
[not found] ` <3SjNh-1Yq-3@gated-at.bofh.it>
[not found] ` <3Ss48-qG-1@gated-at.bofh.it>
[not found] ` <3SxGA-5mR-29@gated-at.bofh.it>
2005-04-12 21:52 ` Bodo Eggert <harvested.in.lkml@posting.7eggert.dyndns.org>
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=425EC778.4070009@tin.it \
--to=senseiwa@tin.it \
--cc=bunk@stusta.de \
--cc=david.lang@digitalinsight.com \
--cc=khc@pm.waw.pl \
--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