From: Ray Olszewski <ray@comarre.com>
To: linux-newbie@vger.kernel.org
Subject: Re: dmesg output: impending hardware failure?
Date: Wed, 17 Aug 2005 17:06:19 -0700 [thread overview]
Message-ID: <4303D0FB.3040003@comarre.com> (raw)
In-Reply-To: <Pine.LNX.4.61.0508171138430.4988@localhost.localdomain>
James Miller wrote:
[...]
> On
> the Synaptic issue: you are undoubtedly aware that Synaptic is a
> graphical frontend for apt, I suppose?
Actually, no. I always use apt from the command line so I missed this
front end. oops.
[...]
>I really didn't want an
> updated kernel since I run vmware and have to recompile modules for it
> every time a new kernel comes along, and I'm not entirely sure how I got
> the kernel. I've looked at packages on the system and can't see where
> new 2.6.x kernels are supposed to be part of my dist-upgrade, but that's
> another issue.
How did you install the kernel? That is, did you install the general 2.6
package for your architecture (kernel-image-2.6-386, for example) or did
you install a specific kernel minor version (for example,
kernel-image-2.6.8-2-386)?
If you did it the first way, that's why you are getting the updates ...
every time a new kernel package is introduced, the general packages
(which Debian calls "transition" packages for reasons I do not know) are
updated to point to the new version. So apt-get dist-upgrade (maybe even
an apt-get upgrade) will upgrade this package just like any other.
If you did it the second way, it should not be happening (at least the
way I understand the apt-get [dist-]upgrade process to work) except when
a new version of that specific kernel is introduced, so I can't be of help.
If the question doesn't mean anything to you, do an "apt-cache search
kernel-image-2.6" and look at some of the package descriptions for the
packages it lists.
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs
next prev parent reply other threads:[~2005-08-18 0:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-15 22:30 dmesg output: impending hardware failure? James Miller
2005-08-15 23:52 ` chuck gelm
2005-08-16 18:26 ` James Miller
2005-08-17 16:33 ` Ray Olszewski
2005-08-17 16:59 ` James Miller
2005-08-18 0:06 ` Ray Olszewski [this message]
2005-08-18 1:41 ` James Miller
2005-08-18 3:06 ` Vikas
2005-08-18 3:10 ` HOW TO HAVE GOOD KERNEL UNDERSTANDING Vikas
2005-08-19 13:07 ` _z33
2005-08-19 13:17 ` osk
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=4303D0FB.3040003@comarre.com \
--to=ray@comarre.com \
--cc=linux-newbie@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