Hi bookie,

I have not heard of slackcurrent. Right now
slackpkg is the one slackware uses to update installed packages and security fixes. But if slackcurrent has worked for you, by all means use it. The 2.6 modules is on the third disc. Yu need to download cd 3.

This disc has extra software you can install. No need to compile. These are
precomiple binaries. All you need to install them is with one command.

installpkg package-name.xxx.tgz

I hope you get a chance to listen to the rest of the audio, as he explains installing the 2.6 kernel and removing the
2.4 kernel sources and modules.

Which is probably causing slackpkg to
conflict with packages for the 2.4 and 2.6
sources.

later...

A little upgrade problem
 

I have used the slackpkg on slackware cd2. That version was a little old, so I downloaded the latest and upgraded the pkg. My problem is that slackpkg want me to upgrade the slackpkg.conf before I can update. I am not sure how I should do this? Any ideas.

bookie

Late update
 

Hi again, almost forgot to post result of all the problems. Well, I listened to the audio that dv502 suggested and then removed the old kernel modules,ide,and headers. Slackpkg seems to be working fine now.

I have a little querry regarding the use of slackpkg. When you have updated your packages slackpkg gives you some options regarding files to be over written or removed:
(K) keep the old files and consider .newfiles later
(O) over write all the old files with the new ones. The old files will be stored with the suffix.org
(R) remove all the .newfiles
(P) prompt k,o,r selection for every file.

What do you want to do?


Being a novice I really don't know what to do for the best. Can someone advise me, please!

bookie

It depends...
 

For example, if you had samba all setup with your workgroup name and shares. And
lets say slackpkg had a update of samba
available. If you selected overwrite, slackpkg will replace your original
configurationn file(s) for samba with a newer default version. Which means you have to repeat setting up samba again.

slackpkg has updated the packages, it just wants to know if you want to keep the
configuration file(s) or replace them
with newer ones with default values.

If slackware is a fresh installed and you ran slackpkg, I would overwrite the old files.

If you had slackware for quite sone time,
and install programs, configured services like samba, apache, mysql, etc...
then I would keep the the original configurations files.

Anyway, if you elect to overwrite. slackpkg will make a backup copy
with the org suffix. So the configuration file for samba is /etc/samba/smb.conf will make a backup copy to /etc/samba/smb.conf.org

Good Luck

Thanks dv502
 

Well, now I understand a little more.
Thanks again.
bookie

You should edit the slackpkg blacklist file and uncomment the entries pertaining to the kernel and headers. You don't want it to mess with those. That's something you should only do manually.

reply
 

Thanks for the extra info masonm.

bookie

You're welcome bookie. Glad to help out.