From: "Jeremy Jackson" <jerj@coplanar.net>
To: <steve.cameron@hp.com>, <linux-kernel@vger.kernel.org>
Subject: Re: How to identify contents of /lib/modules/*
Date: Wed, 16 Apr 2003 13:08:28 -0400 [thread overview]
Message-ID: <005901c3043a$ccc431d0$7c07a8c0@kennet.coplanar.net> (raw)
In-Reply-To: <20030416020059.GA27314@zuul.cca.cpqcorp.net>
You should definitely mention this to your distribution creator. IMHO, it's
seriously broken if uname -r isn't distinct. Debian is unfortunately a
victim of this; I have modded my kernel-image source package to *fix* it. I
don't recall RedHat having this problem, but other RPM based I don't know.
Can you say what your distro is?
Cheers,
Jeremy
----- Original Message -----
From: "Stephen Cameron" <steve.cameron@hp.com>
To: <linux-kernel@vger.kernel.org>
Sent: Tuesday, April 15, 2003 10:00 PM
Subject: How to identify contents of /lib/modules/*
>
> Hi, here's a problem I'm having, perhaps someone has some smart idea...
>
> A certain major linux distribution distributes a number of binary
> kernels, errata kernels, which all report the exact same thing
> via "uname -r". These kernels may differ by only a little
> (only the .config file is different in some small way) or by
> a lot (binary drivers for one don't work (panic) on another).
next prev parent reply other threads:[~2003-04-16 16:54 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-16 2:00 Stephen Cameron
2003-04-16 14:21 ` Alan Cox
2003-04-16 16:06 ` Dominik Kubla
2003-04-17 18:08 ` Kristofer T. Karas
2003-04-16 15:18 ` Arjan van de Ven
2003-04-16 17:08 ` Jeremy Jackson [this message]
2003-04-16 17:20 ` Paul Clements
2003-04-16 15:58 Cameron, Steve
2003-04-16 16:01 ` Alan Cox
2003-04-16 20:54 ` Henning P. Schmiedehausen
2003-04-16 18:57 Cameron, Steve
2003-04-17 20:02 Perez-Gonzalez, Inaky
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='005901c3043a$ccc431d0$7c07a8c0@kennet.coplanar.net' \
--to=jerj@coplanar.net \
--cc=linux-kernel@vger.kernel.org \
--cc=steve.cameron@hp.com \
/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
all inboxes | Powered by JetHome®