As I understand the env command documentation the subcommand style is
preferred, though the old format is still fully supported.
Signed-off-by: Fiona Klute <fiona.kl...@gmx.de>
---
doc/usage/netconsole.rst | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/doc/usage/netconsole.rst b/doc/usage/netconsole.rst
index 0c983e6970..b5832843f3 100644
--- a/doc/usage/netconsole.rst
+++ b/doc/usage/netconsole.rst
@@ -24,9 +24,9 @@ can be used for network console.
For example, if your server IP is 192.168.1.1, you could use::
- => setenv nc 'setenv stdout nc;setenv stdin nc'
- => setenv ncip 192.168.1.1
- => saveenv
+ => env set nc 'env set stdout nc; env set stdin nc'
+ => env set ncip 192.168.1.1
+ => env save
=> run nc
On the host side, please use this script to access the console
--
2.43.0
