From: Stanislav Ievlev <inger@altlinux.org>
To: sisyphus@altlinux.ru
Subject: Re: [sisyphus] Master 2.2 upgrade
Date: Thu, 18 Sep 2003 11:35:08 +0400
Message-ID: <20030918073508.GF15754@basalt.office.altlinux.org> (raw)
In-Reply-To: <200309180930.43636.combr@vesna.ru>
On Thu, Sep 18, 2003 at 09:30:43AM +0500, Mike Lykov wrote:
> Здравствуйте.
>
> Решил проапгрейдить мастер в связи со всякими openssh. по apt-get update и
> apt-get upgrade мне выдалось такое:
>
> Fetched 694B in 1s (625B/s)
> Hit ftp://updates.altlinux.com Master/2.2/i586/updates pkglist
> Hit ftp://updates.altlinux.com Master/2.2/i586/updates release
> Hit ftp://updates.altlinux.com Master/2.2/i586/updates srclist
> Reading Package Lists... Done
> Collecting File Provides... Done
> [root@mail apt]# apt-get upgrade
> Reading Package Lists... Done
> Collecting File Provides... Done
> Building Dependency Tree... Done
> The following packages will be upgraded
> file gkrellm glibc glibc-core glibc-devel glibc-gconv-modules glibc-locales
> glibc-nss
> glibc-timezones glibc-utils iconv kernel24-headers klogd libcups libpopt
> libqt3 libssl
> libtcb libwrap mutt nfs-clients nss_tcb openssh openssh-clients
> openssh-server openssl
> pam-config pam_tcb postfix sysklogd syslog-common syslogd tcb-utils unzip
> xinetd zlib
>
> Прокомментируйте, плиз, необходимость менять glibc* , pam* и тому подобные
> основополагающие вещи?
прочитайте архивы security-announce и вопросы отпадут сами собой.
>
> что в них менялось? Каков риск их апгрейдить на работающем сервере?
>
> --
> Mike
> registered linux user #315334
> jabber id: combr@jabber.ru
> _______________________________________________
> Sisyphus mailing list
> Sisyphus@altlinux.ru
> http://altlinux.ru/mailman/listinfo/sisyphus
prev parent reply other threads:[~2003-09-18 7:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-18 4:30 Mike Lykov
2003-09-18 5:04 ` Alexey I. Froloff
2003-09-18 13:12 ` Mike Lykov
2003-09-18 7:35 ` Stanislav Ievlev [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=20030918073508.GF15754@basalt.office.altlinux.org \
--to=inger@altlinux.org \
--cc=sisyphus@altlinux.ru \
/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
ALT Linux Sisyphus discussions
This inbox may be cloned and mirrored by anyone:
git clone --mirror http://lore.altlinux.org/sisyphus/0 sisyphus/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 sisyphus sisyphus/ http://lore.altlinux.org/sisyphus \
sisyphus@altlinux.ru sisyphus@altlinux.org sisyphus@lists.altlinux.org sisyphus@lists.altlinux.ru sisyphus@lists.altlinux.com sisyphus@linuxteam.iplabs.ru sisyphus@list.linux-os.ru
public-inbox-index sisyphus
Example config snippet for mirrors.
Newsgroup available over NNTP:
nntp://lore.altlinux.org/org.altlinux.lists.sisyphus
AGPL code for this site: git clone https://public-inbox.org/public-inbox.git