Модератор: Модераторы разделов
Что-то я DVD-iso найти не могу
Код:
Slackware 12.1 to 12.2 Upgrade HOWTO <volkerdi@slackware.com>
This document explains how to upgrade from Slackware 12.1 to Slackware 12.2.
----------------------------------------------------------------------------
For details of important changes from Slackware 12.1 to 12.2, see the file
'CHANGES_AND_HINTS.TXT'. Thanks to Robby Workman for help with this.
Before you begin, I would strongly recommend making a backup of your
system, or, if not the entire system, at least the /etc directory. You
might find that you need to refer to a few things after the upgrade
process is complete. Back it up, or take your chances.
OK, now that everything is safely backed up, let's proceed. :-)
To do this, you'll need the Slackware 12.2 packages. If these are on a CD,
create a new directory to mount the CD on so that it doesn't get in the way
during the upgrade:
mkdir /packages
mount /dev/cdrom /packages
The packages don't have to be on a CD-ROM, as an alternative you could
copy the slackware directory (the one with the various package
subdirectories in it, basically the "slackware" directory from the install
CD) to someplace like /root/slackware/. The important thing is that you
know where the slackware packages directory is. We'll use /root/slackware
in the following examples.
0. Put your machine in single-user mode:
telinit 1
Note that this is _not_ strictly required, and there have been reports
of success remotely upgrading machines that are still in multiuser
mode. However, more things can do wrong in multiuser, so especially
if you're considering a remote upgrade in multiuser mode, you might
want to clone the machine locally so that you can do a test run to
uncover any problem areas and come up with workarounds for them.
1. Upgrade your glibc shared libraries. This is important, or things
might go haywire during the first part of the upgrade:
upgradepkg /root/slackware/a/glibc-solibs-*.tgz
2. Upgrade your package utilities:
upgradepkg /root/slackware/a/pkgtools-*.tgz
3. Upgrade everything else (and install new packages):
upgradepkg --install-new /root/slackware/*/*.tgz
If you wish to upgrade everything except for the KDEI language
packs for KDE (these take a lot of space and can be dealt with
after the main upgrade more quickly and easily), running this
script in the "slackware" directory will do the trick:
#!/bin/sh
for dir in a ap d e f k kde l n t tcl x xap y; do
( cd $dir; upgradepkg --install-new *.tgz )
done
4. Make sure your system will boot. First, be sure your initrd is up
to date (if you use one). If you use LILO, make sure the paths in
/etc/lilo.conf point to a valid kernel and then type 'lilo' to
reinstall LILO. If you use a USB memory stick to boot, be sure to
copy the new kernel to it in place of the old one.
5. Remove obsolete packages. The CHANGES_AND_HINTS.TXT file should have a
list of these. You may also wish to go into /var/log/packages and take
a look at the package list:
ls -lt | less
You may spot some old, obsolete, or discontinued packages. If so,
you can remove these using 'removepkg'.
6. Fix your config files. Some of the config files in /etc are going to
need your attention. You'll find the new incoming config files on
your system with the ".new" extension. You may need to fill these in
with information from your old config files and then move them over.
Feel brave? You can use this little script to install most of the
.new config files in /etc. If you've made any local changes you'll
need to add them to the newly installed files. Your old config files
will be copied to *.bak. Anyway, it might be an easier starting
point. Here it is:
#!/bin/sh
cd /etc
find . -name "*.new" | while read configfile; do
if [ ! "$configfile" = "./rc.d/rc.inet1.conf.new" \
-a ! "$configfile" = "./rc.d/rc.local.new" \
-a ! "$configfile" = "./group.new" \
-a ! "$configfile" = "./passwd.new" \
-a ! "$configfile" = "./shadow.new" ]; then
cp -a $(echo $configfile | rev | cut -f 2- -d . | rev) \
$(echo $configfile | rev | cut -f 2- -d . | rev).bak 2> /dev/null
mv $configfile $(echo $configfile | rev | cut -f 2- -d . | rev)
fi
done
7. If you use a non-en_US language pack for KDE and you already have it
installed, then you may upgrade it by moving into the slackware/kdei
directory and using this command:
upgradepkg --install-new k*<your KDE locale>*tgz
To have upgradepkg cycle through all of the available packages, and
see which ones need to be upgraded, use this in slakckare/kdei:
upgradepkg *tgz
If your language has been added to KDE since Slackware 12.1, you'll
need to install it using installpkg, or upgradepkg --install-new.
Typically you'll need to make sure that you have installed the
slackware/kdei packages for kde, koffice, and k3b (if you use those).
8. Return to multi-user mode:
telinit 3
At this point you should be running Slackware 12.2. :-)
I wish everyone good luck with this!
---
Patrick Volkerding
volkerdi@slackware.com
) Код: Выделить всё
Name Last Modified Size Type
Parent Directory/ - Directory
README.1st 2008-Dec-10 01:47:43 0.6K application/octet-stream
slackware-12.2-install-d1.iso.asc 2008-Dec-09 14:13:57 0.1K text/plain
slackware-12.2-install-d1.iso.md5 2008-Dec-09 14:13:57 0.1K application/octet-stream
slackware-12.2-install-d2.iso.asc 2008-Dec-09 14:13:57 0.1K text/plain
slackware-12.2-install-d2.iso.md5 2008-Dec-09 14:13:57 0.1K application/octet-stream
slackware-12.2-install-d3.iso.asc 2008-Dec-09 14:13:57 0.1K text/plain
slackware-12.2-install-d3.iso.md5 2008-Dec-09 14:13:57 0.1K application/octet-stream
slackware-12.2-install-dvd.iso.asc 2008-Dec-09 14:13:57 0.1K text/plain
slackware-12.2-install-dvd.iso.md5 2008-Dec-09 14:13:57 0.1K application/octet-stream
slackware-12.2-source-d4.iso.asc 2008-Dec-09 14:13:57 0.1K text/plain
slackware-12.2-source-d4.iso.md5 2008-Dec-09 14:13:57 0.1K application/octet-stream
slackware-12.2-source-d5.iso.asc 2008-Dec-09 14:13:57 0.1K text/plain
slackware-12.2-source-d5.iso.md5 2008-Dec-09 14:13:57 0.1K application/octet-stream
slackware-12.2-source-d6.iso.asc 2008-Dec-09 14:13:57 0.1K text/plain
slackware-12.2-source-d6.iso.md5 2008-Dec-09 14:13:57 0.1K application/octet-streammikluxo писал(а): ↑11.12.2008 11:45Код: Выделить всё
Name Last Modified Size Type Parent Directory/ - Directory README.1st 2008-Dec-10 01:47:43 0.6K application/octet-stream slackware-12.2-install-d1.iso.asc 2008-Dec-09 14:13:57 0.1K text/plain slackware-12.2-install-d1.iso.md5 2008-Dec-09 14:13:57 0.1K application/octet-stream slackware-12.2-install-d2.iso.asc 2008-Dec-09 14:13:57 0.1K text/plain slackware-12.2-install-d2.iso.md5 2008-Dec-09 14:13:57 0.1K application/octet-stream slackware-12.2-install-d3.iso.asc 2008-Dec-09 14:13:57 0.1K text/plain slackware-12.2-install-d3.iso.md5 2008-Dec-09 14:13:57 0.1K application/octet-stream slackware-12.2-install-dvd.iso.asc 2008-Dec-09 14:13:57 0.1K text/plain slackware-12.2-install-dvd.iso.md5 2008-Dec-09 14:13:57 0.1K application/octet-stream slackware-12.2-source-d4.iso.asc 2008-Dec-09 14:13:57 0.1K text/plain slackware-12.2-source-d4.iso.md5 2008-Dec-09 14:13:57 0.1K application/octet-stream slackware-12.2-source-d5.iso.asc 2008-Dec-09 14:13:57 0.1K text/plain slackware-12.2-source-d5.iso.md5 2008-Dec-09 14:13:57 0.1K application/octet-stream slackware-12.2-source-d6.iso.asc 2008-Dec-09 14:13:57 0.1K text/plain slackware-12.2-source-d6.iso.md5 2008-Dec-09 14:13:57 0.1K application/octet-stream
изошников нет. Та же фигня как и с perespim.
Да я уже и по ссылке качаю.
This release brings the system up-to-date without compromising stability or compatibility with the 12.x series.
(asper писал(а): ↑11.12.2008 12:03Вот у меня возникла мысль: зачем её выкачивать если можно просто проапгрейдить.
Вот эта цитата:
This release brings the system up-to-date without compromising stability or compatibility with the 12.x series.
внушает надежду.
Отпишитесь у кого получилось/не_получилось.
13-я слака поспеет!
Посоветуйте, стоит переходить с версии 11.0 на 12.х?
у меня например установлена куча софта поверх оси, который слинкован с существующими библиотеками. к чему прведет замена этих библиотек?Вот у меня возникла мысль: зачем её выкачивать если можно просто проапгрейдить.
Killertester писал(а): ↑11.12.2008 16:38Чёта я недогнал обещали в след версии слаки kde 4 впихнуть а нету
Вот у меня возникла мысль: зачем её выкачивать если можно просто проапгрейдить.
наверно, даж установлю 12.0, чтоб потом проапгрейдить до 12.2 Посоветуйте, стоит переходить с версии 11.0 на 12.х?
так что не надо Чёта я недогнал обещали в след версии слаки kde 4 впихнуть а нету
На обплевание хотите выставить?
pashaa писал(а): ↑11.12.2008 17:47Killertester писал(а): ↑11.12.2008 16:38Чёта я недогнал обещали в след версии слаки kde 4 впихнуть а нету
В Мопс 6.2 впихнули вроде 3 варианта кед. Одна 3 версии и 2 версии 4й. Бета версия Мопса с торрента доступна к скачиванию. http://www.mininova.org/tor/2065284
McLeod095 писал(а): ↑11.12.2008 11:24package upgrade management with slackpkg moved into the main tree
вот это не может не радовать.
только вот сам обновился с помощью этой проги до current
теперь сижу и чешу репу, а стоит ли обновлять ведро. потом просто столько всего опять устанавливать, начиная от дров на видяху и заканчивая виртуальными машинами.
радости нет предела.
This release brings the system up-to-date without compromising stability or compatibility with the 12.x series.
вот только не смог въехать вот в эту строчку
(asper писал(а): ↑12.12.2008 12:30
Очень смешно, имелось ввиду те у кого стоит 12.1 , вначале всё таки пропрейдиться, а потом уже, если не получится, поставиться с образа.
А для того чтоб проапгрейдиться, не надо выкачивать весь образ, а только часть пакетов, которые установленные на старой слаке, так сказать в целях экономии трафика и времени.
