SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I've some doubts about how to update/upgrade packages which I install, the kernel and de distro.
I only know that the packages which are installed with the distro (KDE, Mozilla Firefox, etc.) are updated according to the mailing list in http://www.slackware.com/security. But what does happen with other packages as Chromium or VLC? I installed some of these packages with ./configure > make > sudo make install, not with sbopkg.
In that case you have to do watch for upgrades youself. In any case it makes things simpler to generate packages instead of doing make install. You can use src2pkg or makepkg for that.
In that case you have to do watch for upgrades youself. In any case it makes things simpler to generate packages instead of doing make install. You can use src2pkg or makepkg for that.
makepkg seems to be easy. So, I need a package.tgz or .txz to use makepkg. And what to do after?
If you made the package you just install it. The package manager keeps track of the installed files. This way, if you want to upgrade your system you just make a new package with the newer version and use upgradepkg to install it. That will first remove the old files and then install the new one. Files that are not longer contained in the new package are removed this way, which wouldn't be the case if you upgrade via make install.
If you made the package you just install it. The package manager keeps track of the installed files. This way, if you want to upgrade your system you just make a new package with the newer version and use upgradepkg to install it. That will first remove the old files and then install the new one. Files that are not longer contained in the new package are removed this way, which wouldn't be the case if you upgrade via make install.
So, if I've understood well, to upgrade Chromium, I have to download chromium.tar.bz2, convert it to .tgz and execute makepkg chromium.tgz.
To upgrade your system to 13.37 you should have a look athe the CHANGES_AND_HINTS.TXT file.
It is all explained in there. You will get automatically the 2.6.37.6-kernel when upgrading.
For manually upgrading the kernel you should have a look at the kernel chapter of the SlackBook, which is in general a good source of knowledge about Slackware and Linux in general.
To upgrade your system to 13.37 you should have a look athe the CHANGES_AND_HINTS.TXT file.
It is all explained in there. You will get automatically the 2.6.37.6-kernel when upgrading.
For manually upgrading the kernel you should have a look at the kernel chapter of the SlackBook, which is in general a good source of knowledge about Slackware and Linux in general.
From the same file, one paragraph before your quoted text:
Quote:
The packages don't have to be on a CD-ROM, as an alternative you could
copy the slackware directory (the one with the various package
subdirectories in it, basically the "slackware" or "slackware64" directory
from the install disc) to someplace like /root/slackware/. The important thing
is that you know where the slackware packages directory is. We'll use
/root/slackware in the following examples.
I've upgraded everything. But there're some files in /boot which are "vmlinuz" (which is in lilo.conf from the installation), "vmlinuz-generic-2.6.37.6", "vmlinuz-generic-smp-2.6.37.6-smp", "vmlinuz-huge-2.6.37.6" and "vmlinuz-huge-smp-2.6.37.6-smp". Have I to modify lilo.conf?
EDIT: Well, I've modified lilo.conf adding /boot/vmlinuz-generic-smp-2.6.37.6-smp, but now Slackware doesn't boot. Can I edit lilo.conf from my DVD of Slackware 13.1?
Did you remember to run /sbin/lilo after updating /etc/lilo.conf?
Yes, you can use a previously working lilo.conf. But like with all config files when moving from an older release to a newer one, you might want to run diff on the two files to see if there are any changes to the files other than the custom changes you have made. With such a venerable program like lilo, I doubt that would be the case, but it's always prudent to check.
But what does happen with other packages as Chromium or VLC? I installed some of these packages with ./configure > make > sudo make install, not with sbopkg.
For future reference, Alien-Bob builds Slackware packages for vlc. You can get them here: http://slackware.org.uk/people/alien...ackbuilds/vlc/
He updates them when newer versions of vlc are released as well. They work perfectly as you would expect.
This will save you the need to compile vlc yourself.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.