Lennart Poettering
Lennart Poettering
see my earlier comment, we should probably just implement what suse already does, i.e. honour "nameserver="
/cc @keszybz
> I don't think we should revert changes to the spec: I know that meaning of $BOOT was changed, but the old definition was internally inconsistent. how so? at least...
> And more importantly, it didn't describe what the EFI code was doing. It wasn't?
Text now says: > An OS installer picks the right place for $BOOT as defined above (possibly creating a partition and file system for it) and creates the /loader/entries/ directory...
> We said "`$BOOT/loader/` is the directory containing all files needed > for Type [keszybz#1](https://github.com/keszybz/systemd/pull/1) entries" which is blatantly wrong. I really don't follow here? why do you say "blatantly"...
> Sadly, this doesn't work, because the two > partitions are not interchangeable. sd-boot loads entries from both partitions, > and its configuration, random-seed, etc. only from the ESP. Its...
> Because either or both $ESP/loader/ and $XBOOTLDR/loader could contain files, and have to be merged. Maybe it's a nuance but I consider $BOOT as being more of a concept...
resolved will always begin with the first configured DNS service, and switch to any other only after failures to contact it. If you turn on debug logging in resolved (by...