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 have been running a firewall off this Linux 2.4.22 , slackware 9.1.0 box.
Its was a very basic install with almost nothing extra installed and nothing runing on the box except ssh.
Its been running great for 124 days with not one problem.
My question is,
Should I be addressing any security/kernel/software updates at this time? I read over slackware.com secruity updates and it doesnt seem any of the 2004 list applies to me.
I would consider upgrading to 2.4.26 to take care of that mremap() issue, and just regular patches to things like sendmail and apache, nothing drastic, though
Yes you should. It's not likely that one of the kernel security updates would really affect you, but it is so easy that there really isn't any reason not to. Just download the latest kernel-headers, -ide, -modules, and -source packages and upgradepkg them. Run lilo and reboot. Easy. ssh uses OpenSSL (at least I think so) and it is definitely a good idea to upgrade those packages. Everything else should be okay since you're not running a web or email server.
Sure. Here is the listings from the Slackware package browser. Just follow the links to a description and a link to download. The upgradepkg these, run lilo, and reboot. You'll also need the alsa-driver package compiled for this kernel so it would be a good idea to get that as well. Just search the package browser using current.
You should probably check out the slackware security advisories - or sign up to the mailing list.
If you go to the date just after slackware 9.1 was released, (in 2003), you can look through all the security patches released. It isn't IMPERATIVE that you install these if you're a home user behind a router with no forwarded ports, but if you are running a server of any kind, it is best really to update with the approriate patches
Yeh, I assume when you installed slackware that you did not install the kernel-source package, (I didn't either, I still don't know what it is useful for, somebody tell me please!) so you can't _upgrade_ the package, you must _install_ it :)
Originally posted by SBing Yeh, I assume when you installed slackware that you did not install the kernel-source package, (I didn't either, I still don't know what it is useful for, somebody tell me please!) so you can't _upgrade_ the package, you must _install_ it
Remember to run lilo once you're done!
Steve
The source is necessary when youre compiling driver modules and compiling various programs against a specific kernel. For example, Video card drivers often require the source to build their modules. It is also necessary if you need to recompile your kernel (and you do!)
One note is that upon doing lilo and the reboot the section in my etc /rc.d/rc.local script that states "dhcpcd eth1" did not seem to pick up the proper info.
I could not resolve any public ip's from client machines. When I did an ifconfig on the slackware box I noticed 192.168.100.1 addresses on eth1 plus in the resolv.conf the info for my 5meg cable connection from my provider were not inputed, It simply put in nameserver 192.168.100.1
Well I shut of the modem thinking it was the prob and also rebooted the slackware box.
Still the same thing.
I went away from it for about 30 min and came back and it had renewed the proper dhcp information.
I have never seen this sort of latency. Usally when the system would reboot it would simply obtain the information at startup.
Must be provider realted. Unless I am missing something?
ANyway my main question is....
Aside from the updates above I installed how does one tell from 2003 and 2004 which updates one needs with my 2.4.26 updated kernel
Perhaps you can quickly check mark the ones I may need for a very basic install of slackware, it is simply acting as a internet router.
www.slackware.org
Slackware 9.1 is released 2003-09-26
Therefore you are NOT going to need security packages before that date.
Type:
su
pkgtool
"View"
...wait a few ticks...
Now - if you have a package and it's in the security update list, install it.
The ones you almost definately need are kernel updates and openssl updates (I think anyway)
Note, you don't need to install packages cumulatively, just install the latest patch. Just something to watch on kernels - make sure you have the right version of kernel-modules in line with the right version of kernel - I.E. when you install 2.4.27 (if and when!) make sure you install 2.4.27 modules
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
