On Wed, 21 Aug 2024 11:27:08 +0200 john doe <johndoe65...@mail.com> wrote:
> The below assumes that this is not a regression or a bug for the > debian-boot mailing list. Agreed. > > When I was playing with this, the only way I could get it to work was > by specifying options that are common in `preseed.cfg` and add more > specific options in included CFG files. > > For the sake of clarity `preseed.cfg` could have the name of > `common.cfg` and `node01.cfg`, `node02.cfg` would have specific > configs for node01 and node02 respectively. > This makes it impossible to specify options twice with different > values. The only way I finally got anything to work at all was to have a computer-specific file, in your terms node01.cfg, and a general file, common.cfg, and have common.cfg call node01.cfg. So at d-i boot time, the command line would include "file=/media/common.cfg". The problem is that I must then edit common.cfg for each machine I want to install, something I was hoping to avoid. I would prefer to have node01.cfg et al. call common.cfg. The other problem I found is that even so, overriding does not work with all options. I can specify netcfg/hostname twice (once in each file), but not partman-auto/expert_recipe. Those are the only two I've tested. > > To me the documentation is somewhat misleading and does not match what > you already found out. Yep. I haven't even looked to see if there's a bug report already. I suppose I should do that next. -- Does anybody read signatures any more? https://charlescurley.com https://charlescurley.com/blog/