slackpkg -current. Whats going to happen?
Hey guys, I am trying to find a very complete slackpkg manual, or howto guide or something that is going to give me all the information I am going to need on how to use it correctly.
I am familiar with it, and I have used it to look for packages, and install some things I didn't have in my system. Last night I changed my mirror to a -current mirror for Slackware 13 and did a: Code:
slackpkg update Code:
slackpkg upgrade-all It basically looked like updated versions of the base install that I have on my system now. I am, however a little worried about the kernel and updated kde packages I saw in the list. If I did go ahead and install the kernel packages using slackpkg, would I just treat it as a regular package? Or would it be like doing a kernel update and have to make the bzImage and update LILO and whatnot? Thanks for any help, Paul |
I don't know what you mean by regular package, since the kernel and sources are in a 'regular' package. There is nothing all that special about it, but yes if you do upgrade the kernel to the kernel version of current, you most definitely have to run lilo after in order to boot your new kernel. Also remember to read the changelogs, changes and hints, booting docs when following current.
|
I believe the command to install new packages is something like:
Code:
slackpkg install-new One new change in -current is that the kernel will see your IDE/SATA drives as 'sdx' instead of 'hdx'. You will probably have to adjust your fstab and bootloader accordingly. |
Quote:
http://rlworkman.net/howtos/libata-switchover |
If you upgrade to -current yes there some changes regarding libata. RWorkman has a good howto here:
http://rlworkman.net/howtos/libata-switchover Hitest beat me to it :P |
You will also have to look through the whole of the current changelog as several programs have been removed.
samac |
All times are GMT -5. The time now is 02:27 AM. |