From: Heiko Carstens <heiko.carstens@de.ibm.com>
To: Arjan van de Ven <arjan@infradead.org>
Cc: Lee Revell <rlrevell@joe-job.com>,
devmazumdar <dev@opensound.com>,
linux-kernel@vger.kernel.org
Subject: Re: How to check if kernel sources are installed on a system?
Date: Sun, 28 May 2006 15:03:20 +0200 [thread overview]
Message-ID: <20060528130320.GA10385@osiris.ibm.com> (raw)
In-Reply-To: <1148653797.3579.18.camel@laptopd505.fenrus.org>
> > > How does one check the existence of the kernel source RPM (or deb) on
> > > every single distribution?.
> > >
> > > We know that rpm -qa | grep kernel-source works on Redhat, Fedora,
> > > SuSE, Mandrake and CentOS - how about other RPM based distros? How
> > > about debian based distros?. There doesn't seem to be a a single
> > > conherent naming scheme.
> >
> > I'd really like to see a distro-agnostic way to retrieve the kernel
> > configuration. /proc/config.gz has existed for soem time but many
> > distros inexplicably don't enable it.
>
> /boot/config-`uname -r`
What's the reason for distros to disable /proc/config.gz?
next prev parent reply other threads:[~2006-05-28 13:03 UTC|newest]
Thread overview: 74+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-25 21:19 How to check if kernel sources are installed on a system? devmazumdar
2006-05-25 21:27 ` alan
2006-05-25 21:29 ` Jan-Benedict Glaw
2006-05-25 22:02 ` Lee Revell
2006-05-25 22:15 ` 4Front Technologies
2006-05-25 22:25 ` Lee Revell
2006-05-25 22:34 ` Dave Jones
2006-05-25 22:40 ` Lee Revell
2006-05-25 21:29 ` Valdis.Kletnieks
2006-05-25 21:35 ` Dave Jones
2006-05-25 21:32 ` Michal Piotrowski
2006-05-25 21:34 ` Jeff Garzik
2006-05-25 21:39 ` Jan-Benedict Glaw
2006-05-25 21:42 ` Jeff Garzik
2006-05-26 14:36 ` Jan-Benedict Glaw
2006-05-25 21:44 ` Dave Jones
2006-05-25 22:52 ` Olivier Galibert
2006-05-26 4:23 ` Willy Tarreau
2006-05-26 14:37 ` Jan-Benedict Glaw
2006-05-26 15:01 ` linux-os (Dick Johnson)
2006-05-27 10:47 ` Jesper Juhl
2006-05-25 21:41 ` Dave Jones
2006-05-25 22:29 ` Lee Revell
2006-05-25 22:39 ` 4Front Technologies
2006-05-25 23:06 ` Jesper Juhl
2006-05-25 23:16 ` 4Front Technologies
2006-05-26 0:12 ` Brian F. G. Bidulock
2006-05-25 23:00 ` Diego Calleja
2006-05-26 0:24 ` Måns Rullgård
2006-05-26 14:29 ` Arjan van de Ven
2006-05-26 15:35 ` Brian F. G. Bidulock
2006-05-27 12:21 ` Arjan van de Ven
2006-05-27 19:52 ` Brian F. G. Bidulock
2006-05-27 20:21 ` Arjan van de Ven
2006-05-27 22:21 ` Brian F. G. Bidulock
2006-05-28 8:27 ` Arjan van de Ven
2006-05-28 10:13 ` Brian F. G. Bidulock
2006-05-27 14:41 ` Kyle Moffett
2006-05-27 22:05 ` Brian F. G. Bidulock
2006-05-28 13:03 ` Heiko Carstens [this message]
2006-05-28 13:12 ` Jan-Benedict Glaw
2006-05-28 13:45 ` Heiko Carstens
2006-05-28 17:03 ` Arjan van de Ven
2006-05-28 17:52 ` Lee Revell
2006-05-28 18:12 ` Arjan van de Ven
2006-05-28 18:22 ` Randy.Dunlap
2006-05-28 19:10 ` Willy Tarreau
2006-05-28 19:55 ` Lee Revell
2006-05-28 20:45 ` Jan-Benedict Glaw
2006-05-28 21:27 ` Lee Revell
2006-05-28 21:55 ` Jan-Benedict Glaw
2006-05-28 22:02 ` Lee Revell
2006-05-28 22:38 ` Jan-Benedict Glaw
2006-05-29 12:11 ` Steven Rostedt
2006-05-29 12:38 ` Steven Rostedt
2006-05-29 4:44 ` Brian F. G. Bidulock
2006-05-29 4:52 ` Arjan van de Ven
2006-05-29 5:35 ` 4Front Technologies
2006-05-29 5:46 ` David Miller
2006-05-29 5:59 ` Valdis.Kletnieks
2006-05-29 6:09 ` Willy Tarreau
2006-05-29 6:11 ` Arjan van de Ven
2006-05-29 6:57 ` Brian F. G. Bidulock
2006-05-29 7:01 ` Arjan van de Ven
2006-05-29 7:29 ` Brian F. G. Bidulock
2006-05-29 7:05 ` 4Front Technologies
2006-05-29 7:23 ` Brian F. G. Bidulock
2006-05-29 7:43 ` Valdis.Kletnieks
2006-05-29 12:23 ` Arjan van de Ven
2006-05-29 15:52 ` Christopher Friesen
2006-05-29 16:00 ` Arjan van de Ven
2006-05-28 20:40 ` Jesper Juhl
2006-05-25 22:51 ` Jesper Juhl
2006-05-26 0:09 ` Thomas Backlund
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=20060528130320.GA10385@osiris.ibm.com \
--to=heiko.carstens@de.ibm.com \
--cc=arjan@infradead.org \
--cc=dev@opensound.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rlrevell@joe-job.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.