[...]
> I divide the package in three part :
> - name
> - name-devel
> - name-config
>
> Name contain the file structure,binaries and doc
> Devel like usual
> Config contain any host dependant config file.
>
> Which allow to update the binary without hurting the config file or
updating
> the config file without touching the binaries.
>
> However, I am willing to perform some change after the installation
> For example ethernet card order reorganistation to have the motherbard
card
> always as eth0, etc.
>
> As I don't want a BIG perl file with my postinstall, it is divided in
> script/plugin.
> But to run them I must mount the floppy !!
I still need the vfat module to be loaded to do that !
The automatic section is nice but have some limitation (feel free to
correct/insult me if I am wrong)
If you want all the information on a floppy and a floppy per server, you
want to store your IP, DNS, (+) information on the floppy. The problem is
that if you have a bootable CD with a modified sysconfig file, you don't
want to burn a CD per server to use the automatic keyword !
As well you can not perform more high level configuration action this way.
As well, some post installation action can be server dependant (You don't
allow the same IPCHAINS rules on a DNS and WEB server). Some of those
configuration can be implemented as "config" RPM but it is not always
convinient this way.
As a consequence, I still would like the vfat module to be present before
the postinstall. I can see not reason to not have it. I will not screw
anything ;*)
Feel free to let me know your thought.
Thomas
