** Reply to note from "Visser, Martin (Sydney)" <[EMAIL PROTECTED]> Fri, 4 Oct 2002 12:41:36 +1000
> The *safe* thing is to do "rpm --freshen --test -v *.rpm" this will tell > you exactly what rpm would do, rather than actually do it. (--upgrade > upgrades existing rpm's that are installed and installs any rpm's that > have not been installed. --freshen only installs new versions of > existing rpms. I usually run --upgrade on the packages I know I want to > upgrade) > > If you are satisfied with what rpm tells you it would do, then just run > "rpm --freshen *.rpm" than, Martin rpm --freshen --test -v *.rpm made a LOT of disk activity, but all it said was: Preparing packages for installation... followed by a lot of disk again.. where does it log to ? rpm --freshen *.rpm said: init 2.84 reload and, came back after a while; I restarted the system, it was: 2.4.18.3, now, is 2.4.18.5 i tried rpm --freshen --test -v *.rpm now, it said nothing so, it did upgrade the kernel as well, yes ? so, am I as good as the date on the errata cd ? and, do I only do 'i386/' directory ? (on a P-II) ? thanks again, Voytek Eymont SBT Information Systems Pty Ltd http://www.sbt.net.au/links/ phone +61-2 9310-1144 fax +61-2 9310-1118 -- SLUG - Sydney Linux User's Group - http://slug.org.au/ More Info: http://lists.slug.org.au/listinfo/slug
