Message ID | 20240514202041.386027-2-fiona.klute@gmx.de |
---|---|
State | Superseded |
Delegated to: | Heinrich Schuchardt |
Headers | show |
Series | [1/2] doc: Detailed example for netconsole setup | expand |
On 5/14/24 22:20, Fiona Klute wrote: > 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.klute@gmx.de> Reviewed-by: Heinrich Schuchardt <xypron.glpk@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 >
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
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.klute@gmx.de> --- doc/usage/netconsole.rst | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) -- 2.43.0