mirror of
https://git.proxmox.com/git/pve-manager
synced 2025-08-14 10:28:14 +00:00
07bbb52f76
We have the pvebanner.service in places which ensures this gets called on boot before the getty target. Thus this only had an effect if we changed the nodename to IP mapping _and_ upgraded/reinstalled pve-manager, then switching to another TTY would show the updated IP. But as this a) is for sure not a common triggered path and b) a IP change suggest a reboot either way, and if the user can handle it on their own without a reboot, they should be able to also handle an outdated /etc/issue until the next reboot. Also for PVE ontop of plain Debian a reboot is needed, so that the PVE kernel gets booted, so this shouldn't be an issue ther neither. Signed-off-by: Thomas Lamprecht <t.lamprecht@proxmox.com> |
||
|---|---|---|
| aplinfo | ||
| bin | ||
| debian | ||
| PVE | ||
| www | ||
| .gitignore | ||
| bridgevlan | ||
| bridgevlanport | ||
| country.pl | ||
| defines.mk | ||
| Makefile | ||
| mtu | ||
| pve-apt.conf | ||
| pve-blacklist.conf | ||
| pve-initramfs.conf | ||
| pve-sources.list | ||
| repoid.pl | ||
| spice-example-sh | ||
| vlan | ||
| vlan-down | ||
| vzdump-hook-script.pl | ||
| vzdump.conf | ||