public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Franco \"Sensei\"" <senseiwa@tin.it>
To: Krzysztof Halasa <khc@pm.waw.pl>
Cc: Adrian Bunk <bunk@stusta.de>, linux-kernel@vger.kernel.org
Subject: Re: [INFO] Kernel strict versioning
Date: Thu, 14 Apr 2005 12:04:45 -0500	[thread overview]
Message-ID: <425EA2AD.3050309@tin.it> (raw)
In-Reply-To: <m37jj7hctl.fsf@defiant.localdomain>

[-- Attachment #1: Type: text/plain, Size: 2279 bytes --]

Krzysztof Halasa wrote:
> Yes, but you still can't change .config. You enable SMP, your binary
> compatibility is history. You _have_to_ be able to enable SMP and
> _you_have_ to be able to disable it.
> 
> The following kernel packages are parts of Fedora Core 3:
> kernel-2.6.9-1.667.i586.rpm
> kernel-2.6.9-1.667.i686.rpm
> kernel-smp-2.6.9-1.667.i586.rpm
> kernel-smp-2.6.9-1.667.i686.rpm

That's because SMP makes a different architecture. So, let's not talk 
about SMP, beacuse it's not a problem.

> 4 of them, each with a different ABI. And this is all the same kernel
> major-minor-version-subversion and the same compiler - only the settings
> differ.

Of course. When upgrading to kernel-2.6.10.i586.rpm? Why should you 
screw up the modules you've compiled? They all belong to 2.6 series.

> Being modular has nothing to do with the "problem" (except it's probably
> required, but Linux _is_ modular for some time now).

It gives more freedom to change the implementation resulting in a easy 
mantainance. Modularity make things easy... little things that work, 
isn't it a unix motto? :)

> Not "can". You have to. You don't want the kernel running on your dual
> Athlon MP to power your old Pentium MMX test machine. The modules are
> irrelevant.

Why always SMP! You are talking about porting a SPARC kernel on a 386! 
I'm talking about having the same binary kernel distribution for your 
achitecture, let's say i586, and being able to upgrade the kernel 
without hassles. No person on earth can imagine using a kernel for 
x86_64 on a i486! :)

> You can have it in /boot. In fact, it's not a kernel issue.

I know, I was just wondering why kernel and modules were on different 
locations.

> Actually, because boot can be a small partition, and may lack support
> for, say, long filenames.
> Actually, I put the kernels in /lib/modules/* as well. I have no /boot
> file systems and I like the idea of rm -rf /lib/modules/something
> deleting all files related to a particular kernel.

I always use a /boot partition. Anyway, /boot will always exist as /lib, 
and you can always do a rm -rf /boot/kernel/modules :)

-- 
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 --]

  reply	other threads:[~2005-04-14 17:10 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"
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" [this message]
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=425EA2AD.3050309@tin.it \
    --to=senseiwa@tin.it \
    --cc=bunk@stusta.de \
    --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