Hello, I understand the reasoning, but the behaviour does not seem consistent / coherent with expected behaviour of using preseed for clean installs.
One expects preseed way to honor the preseed file, as the system is a fresh install for automated deployment. If applied over a manually installed, carefully configured system, this behaviour is logic. But for a automated deployment using preseed, I guess not. When one fires an automated deployment using preseed, it is expected to honor preseed file choices. Is there a good way to detect the different procedures of installation? Maybe using a predefined comment on the file registering the previously applied procedure. Regards. Andre Felipe Machado
