John Hearns wrote:
> 
> rpm -qa   gives a list of all packages installed on the system
> Pipe the output of this to to a script which completes the filename with 
> a .rpm extension and pipe that to rpm --install --replacepkgs
> 
> If you are using a remote http server for the packages you'll have to 
> construct a filename of the type
> http://rpm-server/directory/filename.rpm
> 
> 
> 
> 
> The above answer is a bit flippant.
> Does your install manager not allow you to reinstall machines?
> We install clusters from an image, so we would just wipe and re-install 
> from the original master image.
> 
> I can see cases where you would like to reinstall some packages (as I 
> say I have done this myself), but ALL of the packages on a system?
> There are lots of package dependencies - are you confident that RPM is 
> robust enough to handle all of these?
> If you suspect a system has been hacked, you should reinstall, from an 
> image as above or via a kickstart.
> If your think that reinstalling is too difficult, you should seriously 
> be thinking about updating your install method to a PXE-based booting 
> scheme.



Thank you for your reply. Actually I am a home user of GNU/Linux, having migrated from 
Windows about the last summer.

I want to reinstall all SL 4.4 rpms that are already installed, because there were some 
errors of bad tracks some time ago, and I performed a surface scan marking all bad tracks 
via "e2fsck -c -c -C -y". Since then, everything runs quite smoothly and I want to 
reinstall in a case that there were some data on bad tracks, when I performed the surface 
scan and repair.

I do not know much scripting. Regarding rpm dependencies, I suppose that since I want to 
reinstall all packages installed, I will not have any dependency problem, since all 
dependencies of a given package will exist on the system at the time of its reinstallation.