Updating to -current with slackpkg
Hello, I haven't booted my slackware for a while and as I've been looking in the chagelog of slack-cuurent I found that Pat changed glibc version to 2.7. Is it safe to update slackware to -current using slackpkg? Will it require some extra steps? (Hopefully not recompiling all the sw...) I'm asking before the update, because it is hard to ask on the forum with kernel panic already blinking on the screen :)
Thx in advance!
Updating glibc can be tricky. There are other packages that depend on it. If you make sure to update the remaining packages, everything should be okay.
You should probably follow the upgrade procedure Patrick makes when updating to new versions. I use to try and keep my system updated with Current, it's too tedious. I stick with the update for whatever version I'm running, keeps things nice and simple, also knowing that the new packages released are compatible and compiled against the other packages that might not have updates applied to them.
you MUST update the glibc-solibs FIRST
and then you can update the rest using slackpkg or just run upgradepkg *.tgz
it works for me
Do read the glibc2.7 notes in the -current changelog. Go init 1 and be sure you run a 2.6.x kernel before. Otherwise i've encountered zero problems with 2.7, and i've been using it since it came out on current.
I followed steps from UPGrADING.TXT (in slackware-current dir) and nearly everything went fine.
I had some problems with building new nvidia driver module, because (by default) slackware installs sources for smp kernel and I used non-smp one. It gives an error while inserting module:
Thanx for hints...
One question here:
I want to try upgrade my 12.0 to -current.
What do you think is a best way to download all "-current" directory to my hard drive before upgrade?
I've never used -current, but I've heard mention of rsync -- though this may be overkill. I think Alien Bob has some nice scripts to check -current for changes, so you may want to check it out. (Sorry for the lack of information)
I use slackpkg. It is quite smart and updates glibc-solibs and pkgtools first and then the rest, so there should be no problem. So here's how I do it (roughly):
0. backup everything important, Pat recommends /etc directory (+ your documents, of course :)
1. install slackpkg and configure it to use some of the -current mirrors (in /etc/slackpkg/mirrors and /etc/slackpkg/slackpkg.conf)
2. go to singleuser mode:
and make sure you have access to the network (ie use "ping google.com" or sth similar), if not, run /etc/rc.d/rc.inet1 start
3. run slackpkg update
4. run slackpkg upgrade-all
5. run slackpkg install-new
6. run slackpkg clean-system and choose the packages you want to remove (it lists all the installed packages that are not in official repositories)
7. make sure your symbolic links in /boot (System.map, config and vmlinuz) point to new files (and change it if you want to use generic smp kernel instead of huge one)
8. also make sure that /etc/rc.modules points to new rc.modules-'kernel-num' file
9. make initial ramdisk if you use reiserfs, raid or whatever that needs it (very good instructions in /boot/Readme.initrd)
10. run lilo and configure it to use the initrd and the new kernel
11. you can now try to reboot to see if everything works fine...
...then you would probably need to reinstall drivers for your graphic card and configure new Xserver, maybe uninstall kde internationalization packages, koffice or sth like that...
this is how I do it, I do not guarantee that this will work for you, it does for me.
I also recommend reading ftp://ftp.slackware.com/pub/slackwar...nt/UPGRADE.TXT
to see what are slackware official instructions.
It will sync with -current or any version you set it to. It also can automatically create install cds or an install dvd.
|All times are GMT -5. The time now is 05:28 PM.|