NetworkManager/tools/nm-guest-data/etc-motd-vm.in

*** nm-in-vm:

find NetworkManager bind mounted at {{BASEDIR_NM}}
run `nm-env-prepare.sh setup --idx 1` to setup test interfaces

Configure NetworkManager with `contrib/fedora/rpm/configure-for-system.sh`,
subsequent `meson install` will overwrite your system's NetworkManager,
and you can test it with `systemctl daemon-reload ; systemctl restart NetworkManager`.

Run NM-ci tests after creating eth1 with
`nm-env-prepare.sh --prefix eth -i 1 && sleep 1 && nmcli device connect eth1`.
tools: nm-in-container: don't generate files from the script The script was generating the data-* files that later copies to the container. In order to the files being reusable for nm-in-vm, put them as separate files inside the data directory. However, some of the files need the full path to NetworkManager project, which varies for each user. Instead, make a sed replacement on them and generate the actual files that will be copied. Replacement: {{BASEDIR_NM}} -> $BASEDIR_NM Also, rename the files to more descriptive names, using some prefixes that give a hint of where those files will be put, and the .in extension to indicate that they will be processed. 2023-07-21 15:36:22 +02:00			`*** nm-in-vm:`

			`find NetworkManager bind mounted at {{BASEDIR_NM}}`
			run `nm-env-prepare.sh setup --idx 1` to setup test interfaces

all: remove misc mentions of autotools in docs 2024-08-22 13:53:58 +02:00			Configure NetworkManager with `contrib/fedora/rpm/configure-for-system.sh`,
			subsequent `meson install` will overwrite your system's NetworkManager,
tools: nm-in-container: don't generate files from the script The script was generating the data-* files that later copies to the container. In order to the files being reusable for nm-in-vm, put them as separate files inside the data directory. However, some of the files need the full path to NetworkManager project, which varies for each user. Instead, make a sed replacement on them and generate the actual files that will be copied. Replacement: {{BASEDIR_NM}} -> $BASEDIR_NM Also, rename the files to more descriptive names, using some prefixes that give a hint of where those files will be put, and the .in extension to indicate that they will be processed. 2023-07-21 15:36:22 +02:00			and you can test it with `systemctl daemon-reload ; systemctl restart NetworkManager`.

			`Run NM-ci tests after creating eth1 with`
			`nm-env-prepare.sh --prefix eth -i 1 && sleep 1 && nmcli device connect eth1`.