Hi Brad, the whole discussion on updating the master node and clients was actually meant to be limited to the distribution packages, not the OSCAR packages.
In theory the OSCAR packages can be updated the same way, but that's currently not a guaranteed upgrade path. We didn't audit all the OSCAR API scripts' interaction with installed configuration files. It can well be that an OSCAR package update leads to some "resetted" config files. Regards, Erich On Monday 26 June 2006 08:04, Brad Aisa wrote: > It has just occurred to me that I made a mistake -- repos I now think may > need to be left in place, and somehow updated. I am thinking I should have > left my: > tftpboot/oscar/common-rpms > folder as it was, then: > unpack the latest ones into some new folder > then do some magic update thingy telling the command to take from the new > folder and update into the existing folder > > is that right??? > > Maybe you folks could expand the README into two sections: > 1. How to install from scratch (i.e., the current instructions) > 2. How to update an existing oscar install > > Thanks! > > Brad Aisabaisa at brad-aisa dot com Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ Oscar-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/oscar-devel
