All of lore.kernel.org
 help / color / mirror / Atom feed
From: mulyadi.santosa@gmail.com (Mulyadi Santosa)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Debugging the linux kernel core dump
Date: Sun, 7 Aug 2011 00:50:50 +0700	[thread overview]
Message-ID: <CAGdaadb9fKHZrLvROzrW+3nCO=LHc6c9b1XbZXt3ok7aE2brcw@mail.gmail.com> (raw)
In-Reply-To: <CAN1N8TiK_jUiQHSsqi0ceteLwffYTz5Uvh9CYm1k0CWmgpR9Fg@mail.gmail.com>

Hi Akash...

On Sat, Aug 6, 2011 at 12:06, Akash <email2akashjain@gmail.com> wrote:
> Thanks Malyudi. Thats sounds like a reasonable approach. I did try to search
> kernel-debug RPMs for my kernel could not find any. May be I should just
> keep looking.

AFAIK too, in Ubuntu and its derivatives, kernel related packages are
likely named "linux-image".

So maybe you could try that name prefix too.... a hint: since you use
openSuse, try to use zypper "search" facility, so that you could
reduce mistakes

> On that note, I wonder what is the difference between kernel-base,
> kernel-default, kernel-devel, and similar other RPMs.

most of the times, anything named with "kernel" and "devel" usually
means a package that contains the kernel headers file and others
needed to compile a kernel module or anything related to kernel stuff.
it's a stripped down version of full blown kernel source.

kernel base? kernel default? no clear hint there...


-- 
regards,

Mulyadi Santosa
Freelance Linux trainer and consultant

blog: the-hydra.blogspot.com
training: mulyaditraining.blogspot.com

      reply	other threads:[~2011-08-06 17:50 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-05  5:12 Debugging the linux kernel core dump Akash
2011-08-05  5:19 ` amit mehta
2011-08-05  5:23   ` Akash
2011-08-05  6:46     ` amit mehta
2011-08-06  4:23     ` Mulyadi Santosa
2011-08-06  5:06       ` Akash
2011-08-06 17:50         ` Mulyadi Santosa [this message]

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='CAGdaadb9fKHZrLvROzrW+3nCO=LHc6c9b1XbZXt3ok7aE2brcw@mail.gmail.com' \
    --to=mulyadi.santosa@gmail.com \
    --cc=kernelnewbies@lists.kernelnewbies.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 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.