LinuxQuestions.org
View the Most Wanted LQ Wiki articles.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices

Reply
 
Search this Thread
Old 06-27-2004, 08:01 AM   #1
Nichole_knc
Member
 
Registered: Mar 2004
Location: Georgia
Distribution: SlackWare 10.1+, FreeBSD 4.4-5.2, Amiga 1.3,2.1,3.1, Windors XP Pro (makes a fair answering machine)
Posts: 287

Rep: Reputation: 30
Upgraded to Slack 10 without problems. Tips....


I have completed upgrades to all my boxes with Slackware 10.0 without any issues.
I have also done one virgin install to a multi-boot box, again no issues...

The only thing I found and configured out of the upgrade was that Slackware 10 contained software that is less than the versions I have built and installed locally. I find that to be a disappointment for that would indicate that Slack 10 is not totally "current" with all "stable" releases of the various warez available. Yes I understand Slack specific builds but remember mine are Slack specific as they where built to Slack and my machines.

How I upgraded.
First of all got and burned the install iso(s).
Then I used the latest Swaret available from swaret.org. I configured swaret (swaret.conf) to VERSION=10.0, updated the mirror list and REPOS list and set the /mnt/cdrom in the path. I also set slocate as the "find" option as it is a daily.cron job.
I ran a swaret --update then swaret --list and compared the list of available upgrades to my currently installed list. This is where I noted that some of Slack 10s packages where lesser versions than I had installed on my systems. At this point I editted the swaret.conf to EXCLUDE my higher versions. If you are running dropline you should EXCLUDE=*.dl* or you will break dropline. You can upgrade dropline via the dropline-installer. If you are a KDE user and have KDE update options running in the KDE enviroment to keep KDE updated you should EXCLUDE=k*i686* as you may find yourself with a broken KDE install after the Slack 10 upgrade (i486 versions) KDE update (i686 versions). You should also EXCLUDE custom drivers and other mods that directly apply to your system. Also keep the default EXCLUDE=kernel and do the kernel manually this should avoid wrecking any custom kernel builds you have.
Again I ran swaret --update and swaret --list to compare the list again.
Once I was happy with the prepared update material I then preformed a system wide backup.
If you cannot do I system wide backup you should at the very least backup to a tar your *.conf files.
Also you should backup your /etc even after you have tarred the .conf.
Some other helpful stuff [ls -al] every directory to a file, example; ls -al /dev >/someplacesafe/devdir this will give you a list of how things are setup with premissions.
Do a lsmod >/someplacesafe/mymods and dmesg >/someplacesafe/dmesglst. These will give you your current setup.
Once you are happy the you have safely saved your setup to assisted you if something breaks then move on to the actual upgrade.
swaret --upgrade -a (remember from our swaret lessons do this a couple of times)
Go take a nap with your fingers crossed.
After the swaret --upgrade -a do a swaret --dep (also a couple of times) I suggest that you do the --dep interactively and not with the -a option. This will let you know first hand what is missing and what you need. Swaret does not always find lib links that is "states" you need and some that it states you may need are for things you don't even use. So you may have to go get libs yourself and you can avoid wasted disk space with junk you don't even use.
Once done reboot and use your system as you normally do. Hopefully all has gone well. If not and you lost some configure files you have the originals backed up to assist in fixes.

I know this seems like alot and it is. But it can make a troublefree upgrade possible. It has worked for me on 4 systems, 3 of which are active servers done over night and finished the swaret -dep the next morning. Nothing broke nor needed re-configurin'. Looks like I found my happy place...
I hope this helps some of you find yours.
 
Old 06-27-2004, 08:08 AM   #2
Bruce Hill
HCL Maintainer
 
Registered: Jun 2003
Location: Tupelo, MS
Distribution: Gentoo
Posts: 6,926

Rep: Reputation: 124Reputation: 124
When you did the fresh install with Slack 10, did you get the 2.6.7 kernel (and/or the other stuff in the /testing dir) or did you stick with the 2.4.26? Just curious. I got a new Maxtor still in the box, and I'd like to try Slack 10 with 2.6.7 and all the stuff available...
 
Old 06-27-2004, 08:17 AM   #3
bob_smith
LQ Newbie
 
Registered: Jun 2002
Posts: 21

Rep: Reputation: 15
You get the 2.4 kernel when you do a default install
The 2.6.7 is in the /testing directory on the 2nd cd.
It's all in .tgz format so the only thing you have to do is installpkg kernel-2.6.7blah.tgz, cd to /usr/src/linux-2.6.7 and configure your kernel for compilation

Another change I found was that there aint no more xf86config.
X started right away for me after typing startx, cause i couldn't configure it (yet).
Mind you, the highest resolution i could achieve was 1024 x 768, but I'm sure i can fix it to 1200 x 1024 after i either downloaded nvidia's driver, or edited my x configuration.
It was 4:12 AM so i didn't feel like going through alot of hassling

cheers
 
Old 06-27-2004, 08:29 AM   #4
ringwraith
Senior Member
 
Registered: Sep 2003
Location: Indiana
Distribution: Slackware-current
Posts: 1,244

Rep: Reputation: 47
the command is now xorgconfig
 
Old 06-27-2004, 08:36 AM   #5
Bruce Hill
HCL Maintainer
 
Registered: Jun 2003
Location: Tupelo, MS
Distribution: Gentoo
Posts: 6,926

Rep: Reputation: 124Reputation: 124
Quote:
Originally posted by bob_smith

It's all in .tgz format so the only thing you have to do is installpkg kernel-2.6.7blah.tgz, cd to /usr/src/linux-2.6.7 and configure your kernel for compilation
cheers
I'm a little slow, so help me out. I want to do my initial install with 2.6.7, not upgrade after the install. Is this possible? Would I need to untar it and put it on a CD or something before beginning, so when the install asks for a kernel I can point to it?

Also, have you guys tried gcc-3.4.0 and lvm2?
 
Old 06-27-2004, 09:04 AM   #6
Netizen
Member
 
Registered: Sep 2003
Location: Texas
Distribution: Slackware and Ubuntu
Posts: 355

Rep: Reputation: 30
Quote:
Originally posted by bob_smith

Another change I found was that there aint no more xf86config.
It also now xorg.conf

If you do it the old fashion way.
 
Old 06-27-2004, 07:41 PM   #7
Nichole_knc
Member
 
Registered: Mar 2004
Location: Georgia
Distribution: SlackWare 10.1+, FreeBSD 4.4-5.2, Amiga 1.3,2.1,3.1, Windors XP Pro (makes a fair answering machine)
Posts: 287

Original Poster
Rep: Reputation: 30
I did not load the 2.6.7 kernel. The attempts I have made into the 2.6.# have failed to be fruitful.
Also follow certain circles of reading kernels 2.5 > are not considered "production or stable". Then there is the fact that I am tinkering with Beowulf class clustering using openMosix w/PVM as primary server/clent warez as well as my own brew stuff. This requires me to run kernels 2.4.22-2.4.26 as they are considered stable and they are the ones supported with the OpenMosix patches.

So I did not update/upgrade to any Slack release kernels, my 2.4.26 came from kernel.org site. It has been configured for each machine that netboots into the cluster with the openMosix patches and a bit of hand hacking.

As stated previously me and 2.6.# have not got along very well.
 
Old 06-27-2004, 08:40 PM   #8
Bruce Hill
HCL Maintainer
 
Registered: Jun 2003
Location: Tupelo, MS
Distribution: Gentoo
Posts: 6,926

Rep: Reputation: 124Reputation: 124
Thanks. I found a really good compile guide from one of the kernel maintainers. I'll use that if I decide to try 2.6.7.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Just upgraded to Slack 10.1... digitalhead General 9 03-31-2005 11:15 PM
Upgraded to Slack=current, now no sound! Slovak Slackware 15 11-24-2004 11:00 PM
useful tips for installing slack??? detpenguin Slackware 17 05-11-2004 05:59 PM
Mods request for sticky tips for slack aus9 Slackware 8 11-13-2003 05:44 PM
Switching to Slack... some tips? bxb32001 Slackware 10 10-30-2003 07:01 PM


All times are GMT -5. The time now is 11:31 PM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration