Best way to get a new install updated?
 

What is the best way to get a Slackware 12 installation updated? I'm kind of new so I don't know alot of the way of doing things here any help would be appreciated. Thanks.

Shane

The Slackware extra repository at http://packages.slackware.it/browse.php?q=12.0/extra has a package called "slackpkg" it's easy to install and use. Read the man page, it has good information on how to use it. This is only one solution but it has worked well for me.
here is a link to a how-to which gives you an idea of how to do different things including installing software
http://www.howtoforge.com/the_perfec...op_slackware12
this also a good resource.
http://www.linuxquestions.org/questi...it-all-174447/
good luck

If you're going to update to -current, it's advisable to update everything and not just part of -current. There have been some major changes since 12.0, so if you're not experienced with this it might be better to either (a) make or get an iso image of -current, then backup and do a fresh install, or (b) wait for 12.1. It is probably only weeks away, but only God knows for sure ... not even Pat.

___________________________

Are the things you're living for worth Christ dying for?
--- Leonard Ravenhill

@jfxg Thanks!!! I downloaded and installed and updated everything but the kernel, I read something about updating kernels is a little more difficult or you have to update lilo or something. I don't have lilo installed, I'm dual booting, and Ubuntu is controlling my grub I like it that way. :) Thanks for the tip on that, that was great!

@Bruce Hill Thanks, I'm not sure I have a good understanding of how the Slackware setup works as far as 11, 12, and Current. I think I downloaded the version 12, at anyrate I updated with the version 12 mirrors for slackpkg. I think current is like the testing branch if I'm not mistaken?

Thanks for the help!

Shane

My suggestion to you would be to stick with only the security updates and not try to update everything to -current. It will be much easier to maintain your system that way and it will probably be more stable. If you need a newer version of a certain stock package then I suggest using the official slackbuilds to build one. I can elaborate on that if you are interested.

For security updates:
Ideally, you would have a fresh install of the newest slackware (not -current) around the time it first comes out. If you then subscribe to the security mailing list, then you would get an email every time a security update is available. All you do is download the update (faster if you use a mirror closest to you) and then use upgradepkg as root to install it.

If you are updating a slackware install a while after it was originally released then you could simply check the security advisories pages. Just install all the updates that are for your version (start at the first date after your version's release date which is listed on slackware.com's front page).

Even if you use a tool like slackpkg to handle your updates you should read the security advisory pages (or emails if subscribed to the mailing list) so that you are aware of any special actions needed for certain updates. For instance, one of the updates for Slackware 12 is a kernel update. If you don't run lilo after installing it your system will not be be able to boot. That is why I don't recommend using something like slackpkg (at least until you have had more experience with updates)- it forces you to pay a little more attention to what you are doing.

Thanks for the tips!!! I subscribed to the security list. I wondered how to do that too. :) I did already read a post about someone with an unbootable system, and that is why I left off the kernel updates. If I'm not using lilo (which I'm not) then this shouldn't be such a big issue correct? I'm using Grub, and my other Linux OS has control of it. I'm not new to Linux, but certainly don't know the Slack way of doing things either. :)

Shane

Since you are using grub with another Linux distro you should be fine. Just keep in mind that the kernel update changes the symlinks in /boot so update which ever kernel image last that you want to be using. So, for instance, if your /boot/vmlinuz points to your huge kernel and you want to stick with it, then upgrade that one last. This is all assuming, of course, that your menu.lst file points to slackware's vmlinuz.

The doinst.sh file in a slackware package is a script that runs at the end of the install. If you check this file in the kernel upgrade packages you will see what I mean about the symlinks.

I have a couple of scripts that you may find helpful for these purposes. Let me know if you have any questions about them.

Tiny tip: cat /etc/slackware-version should say something like: Slackware 12.0.0 :)
If you were using -current (which i suggest you don't yet since you're still getting familiar with slackware) it would say: Slackware 12.1
Check the etc.SlackBuild
Note line 28: ...etc-$VERSION-$ARCH-$BUILD and line 11: VERSION=12.1

Hi, shadowsnipes.
Can you explain a bit more about kernels?

If i use now kernel-huge-smp-2.6.21.5 and thare is update i just upgrade the package. ok?
If i want to try instead another kernel, like kernel-generic-smp-2.6.21.5, i just install
package kernel-generic-smp-2.6.21.5_smp-i686-2_slack12.0.tgz and thats it? OK?
If i want to update my kernel to current i have to upgrade all my packages? If i go to current->kernels. there is 3 files: System.map.gz,bzImage,config. Do i need this?

I think i am confused. :(

Alright, do a ls -l /boot and look at the files. You should see kernel images (vmlinuz*), configs, and System.maps for all the stock kernels. You should also 3 symlinks for each of those. You grub bootloader, by default, is most likely pointing to the vmlinuz symlink for Slackware, but you can tell it to have all the kernels listed to boot if you desire (just modify /boot/grub/menu.lst).

If you are just using the stock kernels then you can just upgradepkg them all. Just keep in mind that those packages change the three symlinks I mentioned. Whichever one you upgrade last will have the vmlinuz, config, and System.map symlinks pointing to its respective files. The symlinks are simply a convenience, but keep them in mind if grub points to them in its boot options.

I am not sure if you can just use -current's kernel images or not. I wouldn't recommend that in case the newest version is using a new gcc, etc. If you want a newer kernel than the stock Slackware kernel just build your own. There are plenty of threads about how to go about that so I won't go into details about that here.

But yes, whenever you install a kernel you should install the bzImage, System.map, and config file. The config file under /boot is really more just for reference. You can view the config for your current kernel by
or throw it in a file

din, are you using Grub? Sorry, I thought you were shane2peru at first.

If you are using lilo be sure to run lilo after you are done upgrading kernels.

Also, if you plan on using one of the generic kernels be sure that you build an initrd so you filesystem can be loaded at boot. Read /boot/README.initrd for more info about this.

Shadowsnipes, Thanks! I know about symlinks and that is what my Grub points to so I should be fine, however I will make a note of which one I'm booting off of. Thanks!


Very handy! Thanks, I am running 12.0. I really don't have any plans of running the -Current, I'm not much for the unstable stuff, although I do like new stuff.

I appreciate the help! Thanks all!

Shane

Thanks for help.
Somehow kernels is the harder part of linux for me.
But it will change.

Some times help from some one like you
is better than 100 rtfm's . :)

You are doing good work by helping newbies like me ... :newbie:

PS. I use grub for 2 systems. Its slackware and arch. I learn both.
I don't know yet who is better. I think to learn them both
will do the job "to know" linux. :)

PS2. shane2peru! Sorry, i used your topic here for my question.

din,

If you need help learning how to rebuild your kernel, start with my Linux Kernel Rebuild Guide.
Read it all, and then when you're ready to attempt it if you need help, let me know.

Bruce Hill,
Thank you. I will try ...