where are rpms file?

[grocanar]

the installer just bloat my rpm database.

Moreover how can i install the nvidia driver
in 200+ machine in an non interactive
way?

[Andy Mecham]

Binary RPMs are no longer provided; they were replaced with the installer.

Moreover how can i install the nvidia driver
in 200+ machine in an non interactive
way?

Use the -s option to the installer.

--andy

[bwkaz]

Originally posted by grocanar
the installer just bloat my rpm database.

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.

Moreover how can i install the nvidia driver in 200+ machine in an non interactive way?

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.

[grocanar]

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
rpm database.
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
identical needs.
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
http://www.int-evry.fr/mci/user/doutrele/linux/
That s why i need to have that drivers in
rpm format.
i don't need a binary rpm but a source rpm
is highly needed.

[bwkaz]

Originally posted by grocanar
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 rpm database.
Therefore i can't trust anymore my rpm database then it s bloated.

No, that's not "bloated". That's "not up to date", or "not correct". "Bloated" means that it's bigger than it needs to be, which is not what's going on here.

I guess you re a lucky guy to have 200+ identical system with people who have identical needs. 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. That s why i need to have that drivers in rpm format. i don't need a binary rpm but a source rpm is highly needed.

You can't modify whatever you're using to run the installer manually? Instead of having it run "rpmbuild", have it run "sh filename -s". Doesn't sound too difficult to me...

[grocanar]

Originally posted by bwkaz
No, that's not "bloated". That's "not up to date", or "not correct". "Bloated" means that it's bigger than it needs to be, which is not what's going on here.

Ok i guess i have to improbe my english a bit more.

You can't modify whatever you're using to run the installer manually? Instead of having it run "rpmbuild", have it run "sh filename -s". Doesn't sound too difficult to me...

Well it s a bit more complicated.
I don't have kernel source on all my machine
as i m a bit out of disk on some machine.
I did maintain some different rpm binary
for different combinaison of custom kernel
on a server.

THE SRPM file was so cool to use for a big
network why did u remove it?

[Andy Mecham]

The installer supports all the kernels that the binary RPMs did without recompilation. All you need on the system is a linker. For the systems that you used the SRPMs for before, just use the -s option to the installer.

--andy