ALT Linux users (in English only)
 help / color / mirror / Atom feed
From: Michael Shigorin <>
To: ALT Linux Community <>
Subject: Re: [Comm-en] New Kernel Packages
Date: Thu, 8 Jan 2004 08:19:40 +0200
Message-ID: <> (raw)
In-Reply-To: <1073518596.8239.3.camel@VirtualSkyNet>

On Wed, Jan 07, 2004 at 05:36:36PM -0600, D&J Bouley wrote:
> I know this may be a silly question, but could someone explain
> how the updating of the Kernel packages work?

"By hand" -- kernel is special enough (booting gets modified and
is needed) not to update it automatically.

> I noticed on the ALT Security Announce Archive page the
> mentioning of new Kernel packages.  I've updated Synaptic and
> the new packages are there, however the automatic update
> feature of Synaptic doesn't seem to flag them for updating.

You have to select appropriate packages manually.  They may be
kernel24-up, and depending on used modules -- alsa24-up,
fglrx_kernel-up, NVIDIA_kernel-up, slmdm_kernel-up for
Master/Junior 2.2 series, or kernel-image-std-up and appropriate
kernel-modules-*-std-up for Compact 2.3 beta.

In the latter case packages are to be taken from Sisyphus as the
distro hasn't been released yet hence no updates/.

> Is there a reason for this?  Is the updating of the Kernel
> something I have to initiate myself (through Synaptic) or is it
> safer not to do so, using Junior 2.2 (better to wait for the
> official release of Compact)?

Ummm... if you have untrusted local users, it's far better to run
2.4.20-alt11+ or 2.4.22-alt15+ as exploits are available.  If
not, then having a way of getting root from e.g. named user is
not a sugar too.

"Poor, poor linux kernel..." (almost robinsoniana)

 ---- WBR, Michael Shigorin <>
  ------ Linux.Kiev

      reply	other threads:[~2004-01-08  6:19 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-07 23:36 D&J Bouley
2004-01-08  6:19 ` Michael Shigorin [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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

ALT Linux users (in English only)

This inbox may be cloned and mirrored by anyone:

	git clone --mirror community-en/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 community-en community-en/ \
	public-inbox-index community-en

Example config snippet for mirrors.
Newsgroup available over NNTP:

AGPL code for this site: git clone