Closed sensslen closed 2 years ago
I just found out the hard way that with the changes in this PR no more modifications can be made to the original resolv.conf file (which I need to do unfortunately).
Does anybody know of any possible solutions to this?
I agree with your hesitation. For now I encounter #54 which makes the current state of pimod unusable for me. The only way to resolve the issue (I do also need to modify resolv.conf) in a timely manner was for me to execute the modifications in this PR. I'd be more than happy to learn about alternative/better solutions to this problem.
One alternate solution I can think of is to spin a complete virtual machine in which the modifications to the raspberry Pi are executed. This has the drawback of being slower. Furthermore I don't have enough knowledge to implement such a solution.
With this PR we make sure that the host's resolv.conf is used in any case during chroot. I don't see why the mechanism used to do this differently. In any case: this fixes #54.