Originally posted by bwkaz
Bull. The installer CANNOT bloat any RPM database; it does not enter any information into the RPM database! The state of your RPM database before and after installing the driver is exactly the same.
Well it bloat the rpm database as there s
some file on the system which are not
configuration file and they re not in my
Therefore i can't trust anymore my rpm
database then it s bloated.
Install it once (and set up the system like you need it), and then image the drive. Boot off a CD (rescue mode or something) and mount your hard drive somewhere. Then make a tarball of your entire system, and put it on the network somewhere. When you have another system to create, simply boot to the CD again, decompress the tarball back onto the new system's drive, and rewrite the bootloader (if you use grub, you may not even have to do that -- rewrite only if grub hasn't been installed on that drive; for lilo, you'll have to rewrite all the time).
Edit: Or -s, duh.
I guess you re a lucky guy to have 200+
identical system with people who have
Unfortunately it s not my case.
Then all my software are installed with a mix of kickstat + cfengine + autorpm and all
are in RPM format.
if you read french you can have a look at
That s why i need to have that drivers in
i don't need a binary rpm but a source rpm
is highly needed.