On Sat, 2005-03-05 at 09:47, matice@nic.fi wrote:

Greetings

Preliminary :) I have a SuSE 9.1 system which for certain hardware reasons wont be upgraded to 9.1 so i will have to upgrade individual programs as i would have to do the same with SuSE 9.2 :)

suse 9.1 comes with rinetd version 0.61 and the latest version is 0.62 (contains security fixes) now i just downloaded and compiled the newer version and its ok,

what baffles me is that when i look up the rinetd version of suse it says 0.61 syslog bind my question is what is the extension to the version output ( syslog bind) are there things i need to take into consideration as i compile the 0.62 version and deploy it on my suse 9.1 system?

hoping to receive clear answers :)

If there were security issues with a package the security fixes would have been back ported to the package that came with 9.1. These security fixes would have been installed through a YOU update. If you go into add/remove packages and search for rinetd you will probably see that a newer version has been installed then rinetd-0.61-803.i586.rpm. Look at the -803 part and see if it is a higher number. If it is most likely the security patches have been installed. You can also check the description part of the package in YOU to see why it was supplied. SuSE back ports many security fixes to the currently installed version adds a higher -### to the package as supplies it as a YOU update. This is done to lessen the chance that there will be broken packages down the road. Keep in mind that SuSE goes more for stability then bleeding edge. -- Ken Schneider UNIX since 1989, linux since 1994, SuSE since 1998 * Only reply to the list please* "The day Microsoft makes something that doesn't suck is probably the day they start making vacuum cleaners." -Ernst Jan Plugge